X Corp. sent cease-and-desist letters to Nitter operators on August 24, demanding permanent shutdowns of public instances and the project’s repository. By the next day, Nitter’s main service was offline, development had stopped while its creator sought legal advice, and a seven-year-old route for reading X posts without joining X had become legally radioactive.
Nitter was a privacy-focused alternative front end. Its server fetched public posts, removed ads and tracking machinery, and returned lightweight pages with RSS feeds. Readers needed no X account, app, client-side JavaScript, or direct connection to X. The project described a representative profile page as roughly 60 KB, compared with 784 KB from Twitter’s own interface.
That gap explains the conflict. Nitter separated publication from platform membership. X’s letter tries to reunite them.
The alternate front end became access infrastructure
Nitter began as a faster, quieter interface. Its project README lists the practical differences: no JavaScript, no ads, backend-proxied requests, no exposure of a reader’s IP address or browser fingerprint to X, mobile pages, themes, and RSS.
Those features grew heavier as X closed older access routes. TechCrunch reported that the flagship Nitter.net instance went dark temporarily in 2024 after X tightened its API. Later Nitter deployments connected through real X accounts and session tokens. The reader stayed outside X while the proxy carried the account dependency.
That architecture created a narrow bridge between two incompatible systems. On one side sat public posts used by journalists, software projects, transit operators, local authorities, researchers, and ordinary loudmouths. On the other sat a platform increasingly organized around logged-in identity, official interfaces, personalized ads, and paid API access. Nitter translated between them.
The bridge mattered most for people who had already left. In the substantive Hacker News discussion, operators described using Nitter’s RSS endpoint for local breaking news, public-transport notices, vintage-photo archives, and organizational updates that appeared on X faster than on official websites. These are firsthand reports rather than comprehensive usage data. They reveal the category of dependency: institutions publish into a private feed, then outside tools restore the public read path those institutions failed to provide.
The letter targets code, credentials, and the name
The public GitHub issue began as an outage report: every listed instance showed the same rate-limit error. Nitter creator Zedeus replied that operators had received cease-and-desist letters and that the instances would remain down while he awaited legal advice.
TechCrunch reviewed the letter. Its report says X accused Nitter of unlawful API circumvention, scraping X data, and accessing accounts and session tokens in violation of platform rules. X cited the Texas Harmful Access by Computer Act and the federal Lanham Act, then imposed a 5 p.m. Eastern deadline on August 25.
A summary shared from Nitter’s Matrix community listed five demands: permanently remove Nitter.net and the repository, stop using the Twitter and X marks, cease access to X data and copies, delete account credentials and session tokens, and confirm compliance in writing. X also reportedly notified GitHub and the domain registrar.
X’s current Terms of Service expressly prohibit scraping without written permission, automated access outside published interfaces, and workarounds for technical restrictions. Nitter’s own README says it uses an unofficial API and routes every client request through its backend. The factual dispute is therefore concrete. X controls the approved interfaces; Nitter existed to supply an interface X refused to approve.
No court has ruled on X’s claims in this episode. The letter still achieved immediate downtime. For a volunteer-maintained project, the cost of discovering whether a legal theory survives litigation can exceed the cost of writing and hosting the software by several orders of magnitude.
Public speech now inherits a private admission system
A post can be publicly addressable while its usable context remains gated. X still exposes some individual posts and profile fragments to logged-out visitors. Replies, timelines, media, search, and stable browsing vary by page and session. Nitter assembled those fragments into predictable pages and feeds.
The difference appears in who gets to establish the reading conditions. X can require official JavaScript, choose which replies load, place a login prompt, associate activity with an account, alter API prices, or change the unauthenticated view. Nitter gave the reader a plain document and gave operators a feed they could archive or route into another tool.
This is why “scraping” carries too little explanatory weight by itself. The word covers bulk data extraction, search indexing, price monitoring, archival work, research, model training, accessibility tools, and a human opening a cleaner copy of one public post. X’s terms collapse those uses into a permission boundary controlled by X.
Nitter also demonstrates the limits of technical decentralization. The code remains open source. Instances can appear in other jurisdictions. Operators can rotate accounts, proxies, domains, and hosts. Yet the upstream service owns the data path and can identify every bridge as hostile. A distributed set of readers still depends on one centralized publisher.
The project may return after legal review. Other instances may stay online. New proxies will appear because the demand has survived every API restriction so far. The durable consequence has already landed: anonymous read access now carries the same adversarial posture as scraping infrastructure.
When public agencies, transport providers, newsrooms, and public figures treat X as an announcement channel, they inherit that posture on behalf of their audiences. Their messages may be public in intent and private in delivery. An official website, RSS feed, email list, ActivityPub account, or mirrored archive would restore actual redundancy. Posting once to X delegates the public doorway to X’s product and legal departments.