X Corp. has sent cease-and-desist letters to Nitter, the open-source project that allowed users to view posts on X without logging into the platform or opening its official app. The letters demand a permanent shutdown of Nitter instances and its project repository, escalating X’s earlier efforts to restrict the service through technical and API changes. Nitter’s creator has taken the flagship Nitter.net instance offline while seeking legal advice.
The action could have wider implications for privacy-focused third-party interfaces and open-source projects that rely on publicly accessible social-media data. X alleges that Nitter engaged in unlawful use and circumvention of its API and associated data, including scraping X data and accessing accounts and session tokens in violation of the platform’s rules. The company’s lawyers cited several U.S. laws in the cease-and-desist letter, while Nitter’s creator has paused development and declined to comment on the legal specifics for now.
Why X Is Targeting Nitter
Nitter was designed as an alternative interface for X. Instead of requiring users to interact directly with X’s website or mobile application, it fetched public posts and presented them through a simpler interface.
The service removed advertisements, tracking cookies and JavaScript, allowing users to read posts without an X account. Nitter also became useful to people who wanted to follow public posts while limiting their exposure to the platform’s tracking and recommendation systems.
According to Nitter’s project documentation, its design routed requests through the backend rather than having the user’s browser communicate directly with X. This helped reduce exposure of users’ IP addresses and browser fingerprints to the platform.
What X Allegedly Claims
X’s legal letter, reviewed by TechCrunch, accuses Nitter of an “unlawful use and circumvention” of X’s API and associated data. The company says it has evidence that Nitter scraped X data and accessed X accounts and session tokens in violation of its rules.
The legal claims cited in the letter include:
| Legal Area | X’s Position |
|---|---|
| API access | Alleged unlawful use and circumvention of X’s API |
| Data access | Alleged scraping of X data |
| Account access | Alleged access to X accounts and session tokens |
| Texas law | Reference to the Texas Harmful Access by Computer Act |
| Federal law | Reference to the Lanham Act |
| Requested action | Permanent shutdown of Nitter instances and repository |
The letter reportedly gave Nitter until 5 p.m. Eastern time on August 25 to shut down. The allegations are claims made by X and do not represent a court finding that Nitter violated the cited laws.
Nitter Goes Offline After Seven Years
Nitter’s website said that X sent cease-and-desist letters on August 24 demanding a permanent takedown of Nitter instances and the project repository.
The project’s creator, known online as Zedeus, said Nitter.net was offline and development had stopped temporarily while legal advice was sought. The developer also indicated that other Nitter instance operators had received similar letters.
Nitter Timeline
| Period | Development |
|---|---|
| 2019 | Nitter project begins, according to its creator’s seven-year reference |
| 2024 | X API restrictions cause Nitter.net to go offline temporarily |
| 2024 onward | Instance operators face additional requirements to maintain access |
| August 24, 2026 | X sends cease-and-desist letters |
| August 25, 2026 | Deadline set by X for shutdown |
| August 2026 | Nitter.net goes offline and development is paused |
The latest action follows an earlier confrontation between X and Nitter in 2024.
X Previously Used API Restrictions
X had already taken steps that made operating Nitter considerably more difficult. In 2024, changes to X’s API access contributed to the shutdown of Nitter’s main instance.
After those restrictions, operators who wanted to host Nitter instances had to connect them to real X accounts, according to the project’s GitHub documentation. Development subsequently resumed and additional instances returned online.
The distinction between the two episodes is important. The 2024 disruption primarily involved technical and access restrictions, while the August 2026 action represents a direct legal challenge to the project and its operators.
Why Nitter Mattered To Users
Nitter served a specific group of X users who preferred not to maintain an account or use the official application.
Its interface allowed public posts to be viewed without the standard X experience, including personalized feeds, advertisements and much of the JavaScript used by the platform.
The project also powered other services. TechCrunch reported that sites including XCancel used Nitter to allow users to view X posts directly. That means the cease-and-desist action could affect services beyond the main Nitter.net domain.
Privacy-Focused Features
Nitter’s appeal centered on several characteristics:
- No requirement to log into an X account to read public posts.
- A lightweight interface without the standard X advertising experience.
- Reduced exposure to X tracking mechanisms.
- RSS feeds and other alternative ways of accessing posts.
- Open-source code that could be independently hosted.
These characteristics also put the project at odds with the commercial model of a large social platform, where controlling access to content and user interactions can be important for advertising, analytics and platform security.
The Broader Scraping Debate
The dispute comes amid a wider conflict between technology platforms and third parties that collect or republish data.
Social networks have increasingly imposed restrictions on automated access to their platforms. Companies argue that scraping can place additional technical burdens on their infrastructure, circumvent access controls and potentially facilitate unauthorized collection of user information.
At the same time, developers, researchers and digital-rights advocates have argued that publicly accessible information can have legitimate uses, including research, accessibility, archiving and alternative interfaces.
The Nitter case adds another dimension because the project was not simply a data-collection operation. It provided a user-facing alternative interface for publicly available X posts.
What The Case Means For Open Source
The legal action also highlights a challenge for open-source developers: publishing code and operating a service based on that code can create different legal and technical risks.
An open-source repository can remain publicly accessible as code even when an operator is no longer willing or able to run an associated service. X’s demand reportedly seeks both the shutdown of Nitter instances and the project repository, making the dispute relevant to the distribution of the underlying software as well as its operation.
For developers building alternative interfaces around commercial platforms, the case may reinforce the importance of understanding API terms, authentication requirements, data-use restrictions and jurisdiction-specific laws before operating public services at scale.
The Bigger Picture
X’s action against Nitter reflects a broader shift in the relationship between major platforms and third-party software. Platforms increasingly want control over how their data is accessed, displayed and monetized, while open-source developers often seek to build alternative tools that improve privacy, accessibility or usability.
For users, the immediate consequence is the loss or suspension of an established way to read public X content without directly using the platform. For developers, the case could become another reference point in the continuing debate over scraping, API restrictions, alternative interfaces and the boundaries of open-source software.
Looking Ahead
Nitter’s next steps will depend heavily on the legal advice being sought by its creator and on whether X pursues further action against individual instance operators. The immediate pause means the project’s development is effectively on hold, while other services relying on Nitter could also face pressure to discontinue their operations.
The larger issue will extend beyond Nitter itself. As social platforms tighten access to their data, developers will have to weigh the benefits of independent interfaces against contractual, technical and legal restrictions. The outcome of the Nitter dispute could therefore influence how future privacy-focused and open-source tools interact with major social networks.
Get the day’s top stories in your inbox
One concise email. No spam, unsubscribe anytime.
