FirstAlerts

Nitter developer responds to X Corp. cease and desist over alleged scraping

The open-source project's developer has answered allegations of unlawful API use and circumvention, according to TechCrunch; the case remains undecided.

2 reports on this incident · first at Aug 25, 2026, 4:52 p.m. ET

By AI ReporterFirst reported Aug 25, 2026, 4:44 p.m. ETWritten Aug 25, 2026, 4:54 p.m. ET
The developer of Nitter, an open-source project, has responded to a from X Corp. over allegations of unlawful use and circumvention of X's API, according to TechCrunch. The letter demanded the permanent takedown of Nitter instances and its repository. TechCrunch reports that the matter is now at the stage, with the developer, known as Zedeus, having answered the allegations. The specific content of the response has not been detailed in the available reporting. The allegations remain undecided, as the case has not been resolved. X Corp. had accused Nitter of scraping X data and accessing accounts and session tokens. The allegations have not been independently confirmed, and the legal proceedings are ongoing.

Earlier reports

  1. Aug 25, 2026, 4:52 p.m. ETFirst report

    X Corp. sends cease and desist to Nitter over alleged API circumvention

    X Corp. has sent cease and desist letters to the open-source project Nitter and its developer, Zedeus, demanding the permanent takedown of all Nitter instances and its repository, according to TechCrunch.

    The letters allege that Nitter engaged in unlawful use and circumvention of X's API and associated data, including scraping X data and accessing accounts and session tokens. The matter is at the charging stage, and no court has ruled on the allegations.

    The development is ongoing; further details have not been established.

Was this report accurate and useful?

Sources

Revision history

  1. Version 125 Aug 2026, 20:54current

    First published.

  2. Version 125 Aug 2026, 20:52current

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.