It is logical that any page can see my public IP, at least if I do not use a VPN, but it is one thing to be able to see it and another to log this and my data. So why the hell do I use a front-end to see a fucking Tweet, when then I also have to use VPN, Ad/trackerblocker and others to prevent Twitter from possibly logging my visit or putting crap on my computer, what I do anyway?
Resurrecting a dead front-end by putting another front-end on top is simply absurd and causes more problems and privacy attack points than going straight with proper protections.
What do you do on Facebook for example or on others that are even worse than Twitter, where there is no valid front-end? What do you do when Twitter definitively turns off the Nitter code and sends this Twiiit to hell with it, put on a tin cap?
Twitter, without an account, is pretty much unusable. It doesn’t show you follow-up tweets or replies, and sometimes no tweets at all. The choice isn’t “do I access tweets using this or Twitter”, it’s “do I access tweets with this or not at all”. If there’s useful information in a tweet, I don’t have a problem using this service, even if it logs my IP - that’s a pretty normal thing for any service that is big enough to e.g. need rate limiting.
If you already has an account in Twitter, the front-ends are irrelevant, because Musk already has your data and also see that is you, even using a front-end, except you use a VPN, strong fingerprint protection, and other measures. It’s for users without an Twitter account, to avod a data collection and tracking (way more than only the IP) when they follow a link to Twitter in a site.
The point is, if you don’t have a Twitter account, it’s enough with your normal privacy protections you use, if you have an account too, in both cases a Twitter front-end and more an front-end for an Twitter front end is pointless.
It is logical that any page can see my public IP, at least if I do not use a VPN, but it is one thing to be able to see it and another to log this and my data. So why the hell do I use a front-end to see a fucking Tweet, when then I also have to use VPN, Ad/trackerblocker and others to prevent Twitter from possibly logging my visit or putting crap on my computer, what I do anyway? Resurrecting a dead front-end by putting another front-end on top is simply absurd and causes more problems and privacy attack points than going straight with proper protections. What do you do on Facebook for example or on others that are even worse than Twitter, where there is no valid front-end? What do you do when Twitter definitively turns off the Nitter code and sends this Twiiit to hell with it, put on a tin cap?
Twitter, without an account, is pretty much unusable. It doesn’t show you follow-up tweets or replies, and sometimes no tweets at all. The choice isn’t “do I access tweets using this or Twitter”, it’s “do I access tweets with this or not at all”. If there’s useful information in a tweet, I don’t have a problem using this service, even if it logs my IP - that’s a pretty normal thing for any service that is big enough to e.g. need rate limiting.
If you already has an account in Twitter, the front-ends are irrelevant, because Musk already has your data and also see that is you, even using a front-end, except you use a VPN, strong fingerprint protection, and other measures. It’s for users without an Twitter account, to avod a data collection and tracking (way more than only the IP) when they follow a link to Twitter in a site.
Yes, and I obviously don’t have a Twitter account, so what’s your point?
The point is, if you don’t have a Twitter account, it’s enough with your normal privacy protections you use, if you have an account too, in both cases a Twitter front-end and more an front-end for an Twitter front end is pointless.
Yes, and I don’t have an account. So what’s your point?