Nitter and XCancel are dead after X's legal squeeze
Both privacy-friendly front-ends for reading X posts without an account have suspended service, days after X turned a cease-and-desist letter into a working shutdown.
Nitter and XCancel, the two best-known ways to read public posts on X without signing in, are gone — and this time it looks permanent. Nitter's GitHub repository was archived on Friday 11 September, leaving it read-only, and XCancel shut its doors on Monday, telling visitors that "due to a new development in the ongoing legal proceedings, we are required to suspend this service again until further notice".
The trigger was X's cease-and-desist letter, sent last month, which accused Nitter of the "unlawful use and circumvention" of X's API and data — in plain terms, of scraping the network to reach accounts and session tokens in breach of its rules.
What Nitter actually did
Nitter was an open source front-end that fetched public posts from X and then stripped out the parts most people would rather not have: the adverts, the tracking cookies and the JavaScript. You got a fast, plain, readable timeline with no account and no app, and other projects such as XCancel ran the same engine behind a different door.
That is precisely the problem. X wants people reading its posts inside a surface it can monetise, which is why Twitter closed the door on third-party clients back in 2023, taking Twitterrific and Tweetbot with it. Nitter's main instance, Nitter.net, went dark in 2024 after API restrictions tightened; afterwards, hosting an instance required connecting it to a real X account, which is as much of a leash as it sounds.
The pattern, not the incident
Nitter fought rather than folded. After the cease-and-desist it said that, on legal advice, the project would continue, and both services briefly came back in early September. The retreat came days later, and with the repository archived there is no obvious route back.
For anyone in Europe who used these mirrors to follow a public conversation without being tracked, the practical options are now narrower and worse: an account, an app, or a scraper of your own that carries the same legal risk the developers have just decided they cannot afford.
Our opinion
Every few years the open web loses a window like this and everyone acts surprised. The uncomfortable lesson from Nitter is structural rather than legal: a mirror that depends on scraping the thing it is mirroring has no leverage, and being open source does not make it sustainable when the only developer spending money on servers is receiving letters from lawyers. If you value reading public posts without an account, the tooling that survives will be the boring kind — archives, self-hosted copies and open protocols with real institutional backing — not a beautifully clean front-end bolted onto somebody else's API and hoping they never notice.