Nitter: Update Oct 10th seeking funding and legal help
- ID
- 34194
- Status
- summarized
- Published
- 11 Oct 2026, 6:37 PM
- Fetched
- 11 Oct 2026, 10:23 PM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://nitter.net/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 6.0
- Created
- 11 Oct 2026, 10:24 PM
- Tags
- Audience
- developerssaas_startup_founders
What happened
On 24 August 2026 X Corp sent Nitter a cease and desist demanding permanent takedown of Nitter instances and the project's repository, followed by a second letter on 8 September 2026 repeating the same demands and legal threats. Maintainer zedeus says Nitter currently has no legal counsel, and that the 7 September update stating the project would continue with legal representation was based on assurances that turned out to be untrue. The post asks for lawyers, organizations, or funding (Liberapay, Patreon, Ko-fi, plus BTC/ETH/XMR/SOL/ZEC addresses), and the Hacker News thread drew 217 points and 77 comments.
Why it matters
If anything you ship depends on unofficial or reverse-engineered endpoints of a large platform — a Twitter/X frontend, a scraper, a mirror like Nitter — the binding constraint is now legal cost, not engineering: two C&D letters in three weeks and zero counsel means the project can end without a court ever ruling. The retraction is the concrete lesson: a project's own claim of 'we have legal representation' was wrong within a month, so don't treat a maintainer's status post as a dependency guarantee when deciding whether to build on top of it.
Discussion angle
What is the realistic playbook when a platform sends a C&D to a side project — comply, relocate, or crowdfund a defense — and at what point should a team depending on unofficial APIs start hedging?