You are not logged in.
Hi there!
I recently tried adding
twitter.com nitter.net
www.twitter.com nitter.netto my /etc/hosts file, but it doesn't work.
I then tried
104.244.42.193 nitter.netas 104.244.42.193 is the IP address of Twitter according to nslookup. That also didn't work.
Any ideas?
Offline
If you want to redirect from twitter to nitter, you'd have to use the ip from nitter and the twitter domain. You will get TLS/SSL errors since nitter has no valid certificate for the twitter domain.
185.246.188.57 twitter.comA simpler option would be a redirect inside the browser like https://addons.mozilla.org/firefox/addo … y-redirect
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
A simpler option would be a redirect inside the browser like https://addons.mozilla.org/firefox/addo … y-redirect
Excellent idea;), however, may as well choose one that is actively maintained see the chat in this issue: https://github.com/SimonBrazell/privacy … issues/378
github+addons
https://github.com/libredirect/libredirect
https://addons.mozilla.org/en-US/firefo … ent=search
Offline
Even ignoring certificate mismatch, there would be mismatch regarding the `Host` header. Depending on how the target is configured and how it uses the header, it may not be able to handle the connection at all or — though this isn’t expected to be the case with Nitter — may include resources from a wrong address.
Unless you have 3rd party requests to Twitter blocked in your browser, it would also lead to Nitter being bugged each time some webapp running Twitter code is accessed. That is both causing additional load to the service and may break the webapp in a manner more complicated than a blocked request.
That makes such a simple substitution a bad idea and limits you to in-browser solutions.
Offline