Twitter/X to Nitter EN

Twitter/X to Nitter redirects x.com and twitter.com links to a working Nitter frontend before the request leaves your browser, so X does not receive the navigation. Exceptions: X-only pages (home, notifications, messages, settings, login and similar) stay on X, t.co short links are not intercepted, and if seven X links open in one tab within 10 seconds (a redirect loop, or very fast clicking), interception pauses in that tab for 10 seconds.

Instance selection: follows the Nitter Instance Health service (https://status.d420.de/), polled roughly every 15 minutes. It receives no browsing data. Instance choice is weighted by that service's data and by your own past results on your network. No probe traffic is ever sent to Nitter instances.

Preferred instance: click the toolbar icon on a Nitter page to prefer that instance for new redirects. If it fails, normal fallback still applies.

Automatic fallback:
- If the chosen instance is rate limited, errors, or does not render as Nitter, the extension tries the next one.
- If an instance has the requested feature turned off, such as search, the extension moves on to another one without counting it as broken.
- Cloudflare, Anubis and go-away verification pages are waited out instead of switched away from.
- If no instance works, you see a failure page instead of being sent to X.

Privacy: no telemetry, no analytics, no backend run by this project. To detect failures, the extension reads the Nitter pages it is checking, inside your browser. The page content is not stored or sent anywhere. X's share-tracking parameters are removed from redirected links.

Operators see your IP address: each Nitter instance you land on is run by an independent operator who can see your IP address and which pages you open, as with any website. The health service is also run by an operator its site does not name, and it can see your IP address and when you are online. The extension cannot hide either from them.

Source: https://github.com/deroverda/twitter-to-nitter