Twiiit: A tool to find Nitter instances that haven't been ratelimited
Twiiit: A tool to find Nitter instances that haven't been ratelimited
Twiiit picks a random Nitter instance so you can browse Twitter privately.
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?
What in the absolute hell are you talking about with the IP shit? I feel like I've had a stroke.
In normal circumstances, your IP address is always available to each and every server you connect to online to retrieve content from.
Like at a restaurant, you put your order in, they need to know the table you're sitting at to bring the food out to you. The table is your IP here.
This is absolute base line principles of TCP/IP! It's the reason "servers" are called that, they serve the content to you!
You could always have someone else go to the restaurant, then bring the food to wherever you are, that would be the equivalent of a VPN, or a proxy, etc.
But tl;dr- everything you access online sees the IP address for your connection. It's not some security issue that any specific site points that fact out. It's how the internet fucking works.
Sure as hell isn't a red flag in a privacy policy. Most sites leave it out because it's like saying the sky is blue.
I can't even. You get wet if you go swimming. Your IP address is seen if you do anything online.
Copying the user agent string from the network requests tab obviously makes them a cyber security expert, didn’t you know?
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?