Nitter will continue after X Corp cease-and-desist, project says

Nitter reverses course

Nitter, the open-source alternative front-end for Twitter, is back from the brink. According to an update on the project's GitHub repository, the project will carry on after its maintainer took legal advice, with further details promised soon.

The confrontation became public through a note in the repository's README stating that X Corp sent cease-and-desist letters on 24 August 2026 demanding a permanent takedown of both Nitter instances and the project's repository. A Hacker News post on 6 September, headlined to say that Nitter had been unarchived and would continue, points to a commit titled "Update README - Nitter lives". The wording implies the repository had been archived in the interim, and that the wind-down has now been reversed.

What Nitter does

Nitter is a free, privacy-focused front-end for Twitter, licensed under the AGPLv3 and inspired by Invidious, the comparable front-end for YouTube. The README pitches it as a way to read Twitter with no JavaScript, no ads and no direct contact between the visitor's browser and Twitter: every request is proxied through the hosting instance, which the project says stops Twitter from recording a visitor's IP address or browser fingerprint. It works against what the README calls Twitter's unofficial API, so no developer account is needed, and pages are much lighter — the project cites one account page at roughly 60KB served through Nitter against about 784KB from twitter.com.

The project's stated rationale is that Twitter is effectively unusable without JavaScript and, since 2024, without signing up, which leaves privacy-conscious readers with few options. Community-run instances and browser extensions extend that reach, and RSS feeds are supported, although the README notes they are often switched off on individual instances because of abuse.

Quiet changes alongside the announcement

The same commit that revived the project also tidied the repository. Donation details were reorganised, continuous-integration and licence badges were added, and the legal contact line now explicitly covers DMCA requests alongside general legal inquiries. The roadmap is otherwise unchanged: an account system with timeline support, intended to let users follow accounts and get a clean chronological timeline without a Twitter account, plus archiving of tweets and profiles.

Self-hosting remains fully documented. The README describes builds using the Nim language, with Redis or its open-source fork Valkey for caching, and a prebuilt multi-arch Docker image that runs on both amd64 and arm64 hardware.

Why it matters

For privacy-minded users, researchers and anyone reading via RSS, Nitter is a practical way to browse X without an account, advertising or tracking. Its disappearance would have closed off one of the last straightforward routes to that experience, and the community-run instance network would have gone with it.

The legal dimension matters beyond a single project. X Corp demanded the removal of both hosted instances and the source repository itself, a broad ask that reaches past the people operating servers to the act of publishing code. The fact that Nitter's maintainer, after taking legal advice, felt confident enough to unarchive the repository suggests the demand was not viewed as watertight. What the promised follow-up details reveal about that reasoning could shape how other alternative front-ends, which depend on similar unofficial access to platform data, respond when similar letters arrive. For now, the code is public again and the project says it is staying put.