- cross-posted to:
- privacyguides@lemmy.one
- cross-posted to:
- privacyguides@lemmy.one
You must log in or register to comment.
OP: Hello. Here is something useful that searches for alternate front ends that are operational when you need to access privacy invasive services.
ITT: throws a fit because it lets someone to do something they don’t like
This is why us privacy conscious folks are labeled freaks and weirds. Not because we reject privacy invasive services, but we can’t deal with anything that isn’t absolutely perfect.
Just be done with it
Some people will find this useful. Yes, we should really just abandon Twitter in all its forms, but there are legitimate reasons to view its content; and if there’s a way of doing so without compromising our privacy, surely that’s a good thing?
I don’t see the sense to use an front end for an front end to see a Tweet, apart with one whose PP is quite questionable
…Here is an example of a request in the log file:
::ffff:127.0.0.1 - - [14/Feb/2022:00:02:58 +0000] “GET /jack HTTP/1.1” 302 60 “-” “Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.120 Safari/537.36” Using twiiit.com adds a layer where one’s IP is visible. One’s IP is visible to twiiit.com then to whatever Nitter instance twiiit.com redirects the query to. Is this correct?
Yes. When somebody uses the site their IP is visible to the service. Once they are redirected to one of the Nitter instances their IP is visible to that particular instance.
You can use Tor or a VPS to obfuscate your IP address and useragent.
This last is what I can do also without the need to use Nitter and Twiiit apart of the trackerblocker and randomizing fingerprints which I use anyway. Nitter sadly is dead and patch it with an front end don’t fix it at the long therm. Whats the next, another front end for Twiiit to see a Tweet ocassionaly?
