X Corp.'s cease-and-desist letters take Nitter and XCancel offline
Two of the best-known ways to read X posts without an account went dark within hours of each other — both citing letters from X Corp. The no-login era of the timeline is formally ending.
Nitter, the open-source front end that let anyone browse X posts without an account, went offline after its maintainer received a cease-and-desist letter from X Corp. A notice posted on nitter.net by the project's developer, the pseudonymous zedeus, says letters sent on August 24 demand a permanent takedown of Nitter instances and of the project's repository itself. Development has stopped for the time being, he wrote, and he is seeking legal advice before commenting further on specifics. His sign-off thanked the community that used, hosted, packaged, donated to and contributed to Nitter over the past seven years.
XCancel, the other widely used public instance, shut down the same day. Its operator posted that a letter from X Corp. arrived Monday at 8 p.m. EST asking it to cease and desist, that the service is stopped until further notice, and that it too is seeking legal advice — closing two years of operation. TechCrunch reports the letters center on alleged scraping, with other coverage citing unauthorized API and data access as X's stated grounds. X's precise legal theory beyond those allegations hasn't been laid out publicly yet.
For most users Nitter was a convenience; for a slice of the AI and research world it was quiet infrastructure. Journalists, academics, monitoring tools and dataset builders used these front ends to read and collect posts at scale without accounts or paid API access — and X has spent years steadily closing that door with paid API tiers, login walls and rate limits. The letters land as the enforcement endpoint of that strategy: rather than blocking scrapers one by one, X is going after the tools that made scraping easy in the first place.
The genuinely new escalation is the demand against the repository, not just the instances. Sites going dark is whack-a-mole — another mirror can appear next week — but taking down the source code threatens the project outright, and it will test whether code hosting platforms stand behind an open-source project under legal attack. Self-hosting Nitter remains technically possible today, but without the upstream repo, maintenance, security fixes and forks get much harder.
Our take: this fight is bigger than one front end. It asks who is allowed to build an independent window onto a platform at all — and the answer platforms have been converging on is "only us, on our terms." Expect more legal pressure on interoperability and reader projects across the industry, because it's working.
What to watch: whether the repository faces a formal hosting takedown request, whether smaller Nitter instances start reporting letters, and whether either operator contests X's claims rather than folding.
If your research or monitoring workflow leaned on Nitter or XCancel, what's your replacement plan? Tell us in the comments.
