Product2 distinct publishers3 min readPublished
The cease-and-desist gave roughly 21 hours and named the repository, not just the running instances. Account-free reading of X is now a paid API key or a DSA application.
The Product Desk · Product desk
Compiled by The Product DeskSomething wrong?How this is made
A blocked endpoint and a letter from lawyers do different work. In February 2024 X closed several of the methods Nitter used to reach posts, including a guest account feature, and the flagship instance stopped working; hosts reattached their instances to real X accounts, and the service came back in 2025 [12]. Code survives that kind of block. The letters that arrived on 24 August ask for a permanent takedown of Nitter instances and of the project's repository, which has been on GitHub since 2019 [3][14], and the instrument this time is X's lawyers rather than a technical restriction [13].
There is a circularity in the accusation. X says it holds evidence that Nitter scraped its data and reached X accounts and session tokens in breach of its rules [7]. Reaching X accounts is what X's own 2024 change left hosts to do: once the guest method closed, an instance needed a real account behind it [12][2].
The two published readings of the letter do not describe the same demand. Notebookcheck reports the notice as a letter received on 24 August at 8 PM EST asking Nitter to stop operating XCancel [6]. The notice on Nitter's own site, as read by TechCrunch's Sarah Perez, describes a permanent takedown of instances and of the repository, with a deadline of 5pm Eastern on 25 August [3][4][3]. That is about 21 hours of notice [1]. If the wider reading is the operative one, then everyone who packaged or hosted a copy is inside the demand, and the developer has said other instances received similar letters [15].
What teams lose is a fetch path, not content. Nitter pulled public posts and stripped the ads, cookies and JavaScript, so a reader got a page without an account or the app [10]; there was no home feed, no notifications and no way to log in or post [11]. Forums that ban direct links to X leaned on it as the way to quote a post without sending anyone to X [18]. The remaining routes are the official API and, for European work, the Digital Services Act requirement that very large platforms give vetted researchers access [20]. One of those has a price, the other has an application queue.
Whether the claim would win is a separate question from whether the letter works. A US court dismissed Google's scraping claim against SerpApi in July [21], and the statutes X cites, a Texas computer-access law and the federal trademark act, do not obviously reach a server in the European Union [8][19]. Forbes counted nearly all popular instances down by Wednesday morning, with one exception hosted in Singapore [16], and Gizmodo relayed an unconfirmed report of maintainers elsewhere still trying [17]. A next-day deadline does not need a ruling. It needs a host who would rather not find out. X and Musk have not commented on the shutdowns [9].
Ranked by verification strength, evidence, and original report placement.
X Corp has sent cease-and-desist letters to Nitter, the open-source project that let people read X posts without an account; nitter.net is offline and development has stopped.
X gave Nitter until 5pm Eastern on 25 August to shut down, according to TechCrunch's Sarah Perez, who read one of the letters.
XCancel, the most widely shared of the sites running on Nitter, posted that it received a letter from X Corp and is stopping operations until further notice.
Notebookcheck reports that the message shown on XCancel says Nitter received a letter from X Corp on August 24 at 8 PM EST asking it to stop operating XCancel, and that the project has suspended the service while it looks into its legal options.
The letter accuses Nitter of the unlawful use and circumvention of X's API and associated data, and X says it holds evidence that Nitter scraped its data and reached X accounts and session tokens in breach of its rules.
X's lawyers cite the Texas Harmful Access by Computer Act and the Lanham Act, the federal trademark statute, and add that the list is not exhaustive.
Follow any of these and your For You feed starts watching them — no settings page required.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Letter contents second-hand; effects directly observable
The observable facts are strong: both publishers independently confirm the offline services and the site notices, and the allegation language is consistent across them. But no source publishes the letter itself — both rest on TechCrunch's read of one letter — X has not commented, and the two accounts disagree on whether the demand covers the repository and all instances or only XCancel.
Enforcement effect visible across flagship, XCancel and most instances
Real-world effect is directly observed rather than asserted: the flagship instance and XCancel are down, development stopped, and nearly all popular instances were offline within days, leaving one Singapore host. What is missing is any usage measurement — no traffic, instance count, or user numbers appear in the sources — so the breadth of the loss is qualitative.
Mildly overstated on the source-code angle
The shutdown itself is understated if anything — the services really are gone. The overstatement sits in the repository framing: only one of the two publishers reports a repository takedown demand, the other describes a narrower demand to stop operating XCancel, and the repository was still reachable at publication. Similarly, the claim that the letter cannot reach EU or Singapore hosts is analytical rather than tested.
Platform control and ad-tracking incentives documented; publisher incentives unclear
The reporting supplies a coherent incentive account for the enforcing party: restricting third-party readers funnels readers into the official app where tracking and personalised advertising work, a pattern attributed across large social networks and Meta's litigation. X's own earlier technical blocks and the account-attachment requirement fit that direction. Nothing in the sources discloses commercial relationships or funding for either publisher, so their incentives are not assessable.
Effects solid, letter terms and legal outcome open
Confidence is high on what happened and moderate on what the letter says and what follows. Two publishers plus public site notices establish the shutdowns; the letter's scope is contested, X is silent, Zedeus has not said whether he will contest, and the fate of the repository and the surviving offshore instance is unresolved.
invest
X's stablecoin creator payouts would be a plumbing decision, not a crypto bet3 distinct publishers
leadership
Builders put doom at 10 to 50 per cent and expect binding rules only after the disaster1 distinct publisher
invest
The AI deal frame flipped: buy at 15 times revenue, pay with paper marked at 401 distinct publisher
invest
The 81% Problem: AI's Star CEOs Are Polling Badly With The People They Need To Hire1 distinct publisher
Distinct publishers with included, body-backed reporting in this cluster.
1 article · August 25, 2026
1 article · August 26, 2026