X Forces Nitter Offline With Cease-and-Desist Letters Targeting Source Code

X Corp. sent cease-and-desist letters on 24 August 2026 demanding a permanent takedown of Nitter instances and the project's source code repository, with a compliance deadline of 5 p.m. EST on August 25. The flagship Nitter.net instance is now offline, and the project's maintainer expects all instances to remain down while awaiting legal advice (TechCrunch).

Nitter is an open-source project that lets users read X posts without logging into or opening the X app. It also powers third-party sites including XCancel that provide direct viewing of X content. The project, maintained by a developer using the handle Zedeus, has operated as a privacy-oriented alternative front-end for the platform formerly known as Twitter.

TechCrunch viewed the letter from X, which accuses Nitter of unlawful use and circumvention of X's API — the interface that lets software communicate with X's systems — and associated data. X's lawyers claim the company has evidence that Nitter scraped X data and accessed X accounts and session tokens (temporary authentication keys that prove a user is logged in) in violation of X's rules. The letter cites two legal frameworks: the Texas Harmful Access by Computer Act (§§ 143.001, 33.02) and the Lanham Act (15 U.S.C. §§ 1114, 1125), the latter covering trademark infringement and false designation of origin.

Zedeus told TechCrunch by email that other Nitter instance operators also received similar cease-and-desist letters, indicating the legal action extends beyond the primary project to the broader network of community-hosted mirrors.

On the project's official GitHub repository, the maintainer announced that the project had received the letters, is awaiting legal advice, and expects all Nitter instances to remain down (GitHub). The Nitter.net website states that the project is offline while its creator seeks legal counsel.

This is not the first confrontation between X and Nitter. In 2024, Nitter.net went dark temporarily after X rolled out new API restrictions. Following that crackdown, hosts of Nitter instances had to connect them to real X accounts to keep functioning, a workaround that required supplying authenticated session credentials rather than relying on public API access. The current cease-and-desist letters, which allege session token access, suggest X's legal team is now targeting precisely that mechanism.

The citation of the Texas Harmful Access by Computer Act is notable. The statute addresses unauthorized access to computer systems and data, and X's claim that Nitter accessed session tokens, if accurate, goes beyond conventional scraping of public-facing content into territory involving authenticated credentials. The Lanham Act claims add a trademark dimension, likely targeting Nitter's branding or the possibility that third-party instances create consumer confusion about affiliation with X.

The broader context here is one of accelerating platform enclosure around social media data. X's API restrictions beginning in 2023 eliminated free-tier access for most developers and researchers. Nitter survived those changes by shifting to authenticated account connections, but that approach now appears to be the specific conduct X is challenging legally. For developers who maintain alternative front-ends or rely on platform data for research, archival, or accessibility purposes, the legal theories X is advancing — particularly the computer fraud and session token claims — establish a framework that could be applied to other projects operating in similar technical territory.

The open-source nature of Nitter complicates any takedown effort. Even if the primary repository is removed and the flagship instance stays dark, the codebase has been publicly available for years and has been forked and distributed widely. Community-hosted instances operating outside U.S. jurisdiction present enforcement challenges that a single cease-and-desist letter cannot address. At the same time, X's decision to target the project at the source level, demanding removal of the repository itself rather than just individual instances, signals an intent to suppress the tool's availability entirely rather than play whack-a-mole with individual mirrors.

For the research community, Nitter has served as more than a convenience reader. It provided a way to reference and archive X posts without JavaScript, without tracking, and without an account — properties valued by journalists, archivists, and accessibility advocates. If the project is permanently shuttered, those use cases lose their primary tool, and no direct equivalent currently fills that niche with the same combination of open-source transparency and community-hosted resilience.