Nitter is a free, open-source, self-hosted Twitter/X front-end that emphasizes privacy, speed, and minimalism.
Nitter is an alternative front-end for Twitter/X built in Nim. It is designed to be hosted by users or communities rather than used as an official Twitter product, and the README describes it as focused on privacy and performance. The project also points to a community-maintained ecosystem of instances and browser extensions.
The repository is addressing the difficulty of using Twitter without JavaScript, as well as the privacy concerns that come from analytics, IP-based tracking, and browser fingerprinting. The README says Nitter is meant to let people browse Twitter without needing a Twitter account or exposing their browser to Twitter’s tracking surface in the same way a normal web session does.
At a high level, Nitter sits between the user and Twitter: the client talks to Nitter’s backend, and the backend fetches Twitter data on the user’s behalf. The README says this keeps the browser from talking directly to Twitter, avoids JavaScript on the client side, and relies on Twitter’s unofficial API rather than a developer account. It also supports features like RSS feeds, themes, and responsive mobile layouts, with some instance-level limitations noted in the README such as RSS sometimes being disabled due to abuse.
Its current attention appears tied to two things in the README and metadata: a strong privacy-centered use case and a recent legal notice from X Corp. The repository notes that cease-and-desist letters were sent on 24 August 2026 requesting takedown of Nitter instances and the repository, while also stating the project will continue after legal advice. Combined with the recent monthly star gain, that makes it more visible right now.
The README itself names Invidious as the project that inspired Nitter, suggesting a similar approach of an alternative front-end for a large platform. It also mentions that users often combine Nitter with tools like VPNs, uBlock/uMatrix, and browser privacy protections, though those are privacy measures rather than direct replacements. Beyond that, the README does not compare Nitter to other specific Twitter front-ends.
AI-explained · grounded in each repo's README