Privacy: catch x.com before rather than after it redirects to twitter.com
Opened this issue · 0 comments
pseudomonas commented
At the moment, a link to x.com is passed to x.com, which issues a redirect to twitter.com (injecting a tracking parameter by the by) and then that second link is intercepted by this package and translated to nitter.net.
This means that the process leaves a trace on the X/Twitter servers, which is suboptimal for privacy purposes; it would be better if this app intercepted requests to x.com in the same way it intercepts those to twitter.com,