X Sends Cease-and-Desist Letters to Ad-Free Viewing Tools Nitter and XCancel, Forcing Both Offline

On August 24, 2026, the company sent cease-and-desist letters to Nitter, which let people read X posts without an account, and to XCancel, a separately branded service built on Nitter's code, demanding both go permanently offline by 5 p.m.

What the record actually shows is narrower: a takedown demand, a shutdown, and a one-line promise of continuation with no terms attached. Whether that promise survives contact with X's underlying legal claims — that Nitter engaged in "unlawful use and circumvention" of X's API and accessed accounts and session tokens without authorization, per The Next Web's summary of the letter — is not something any source yet answers.

What X's letters actually demand

The cease-and-desist letters, sent by X Corp's lawyers, ask for a "permanent takedown of Nitter instances and of the project's repository," according to The Next Web. They cite the Texas Harmful Access by Computer Act and the Lanham Act, the federal trademark statute, as grounds — a combination that reaches beyond a simple terms-of-service dispute into computer-crime and brand-misuse law. The Register's report frames the action as coming from "the social media mouthpiece of free speech absolutist Elon Musk," a characterization that underscores the tension the paper sees between X's stated free-speech posture and legal action against a read-only, ad-free viewing tool, but the article does not report any public comment from Musk or X Corp beyond the letters themselves.

Nitter's own response was procedural rather than substantive. Zedeus wrote that "nitter.net is offline and development has stopped for the time being," adding that he was "seeking legal advice and won't be commenting further on the specifics for now," according to The Register.

How the workaround worked, and why it stopped being free

Nitter's proposition to users rested on a simple trade: it fetched public X posts through what its own documentation called "Twitter's unofficial API," and no developer account was required, according to the project's GitHub page. All requests routed through Nitter's own backend rather than the user's browser talking to X directly, which is what let it withhold users' IP addresses and browser fingerprints from X.

That architecture stopped being simple in 2024. X rolled out API restrictions that took nitter.net offline temporarily, and Nitter's response, according to TechCrunch, was to require instance operators to connect each deployment to a real X account in order to keep functioning. No source describes whether those connected accounts belonged to volunteers, to Nitter's maintainers, or to arrangements X now considers to have exceeded their scope; that gap is central to assessing how serious the allegation is, and it remains unfilled.

What happened to the code once the letters landed

The repository was set to archived and read-only, according to The Register, a state that blocks new commits, pull requests and issue submissions while leaving the existing code publicly visible; no source reports who set that status or whether GitHub itself took any action. That is a soft form of compliance distinct from deletion — the code did not disappear, but the collaborative mechanism that let volunteers patch it in response to X's next technical change did, at least for a period. Open Source For You's coverage confirms the same cease-and-desist letters were sent to Nitter and multiple downstream instances, framing the action around alleged API circumvention and data scraping, but adds no detail on the archive status or on what "will continue" is expected to mean in practice.

The limits of the comparison to other alternative platforms

A separate body of research bears on how hard it is for users to leave a dominant platform for an alternative, though it examines a different model than Nitter's. The Engine Room's 2024 report on social justice organizations in the Majority World, prepared with support from the Open Society Foundation, examined attempts to migrate from mainstream platforms to alternatives including Mastodon and Bluesky. It found a higher technological barrier to entry for those alternatives than for the incumbents they were meant to replace — a finding about the cost of migrating to a new platform, which is not the model Nitter used. Nitter's own model never asked users to migrate anywhere; it asked them to read X's content through a different pipe, one that X's cease-and-desist letters now allege depended on unauthorized access to accounts and session tokens.

Whether "the project will continue" means a new data-access method that avoids the API and account dependencies X now objects to, a relocation to a jurisdiction less exposed to the Texas Harmful Access by Computer Act, or a licensing arrangement with X itself is not stated in the GitHub notice, and no subsequent announcement has been reported.