Nitter commit 1428b4c2 restores continuation notice after X Corp cease-and-desist
Nitter resumes after legal review of X Corp demands. The commit shows open-source frontends can persist when code distribution stays within AGPL boundaries. Instance survival now hinges on rapid relocation rather than project shutdown.
The commit replaces the takedown note with an explicit statement that the project will continue operations. Repository files show removal of prior shutdown language and retention of all feature descriptions including backend-only requests and AGPLv3 licensing. No new code commits accompanied the change.
Prior Nitter instances had already faced repeated blocks from X's rate limits and API modifications documented in the project's issue history since 2023. Similar patterns appear in the Invidious repository where legal correspondence prompted instance operators to shift hosting jurisdictions rather than shut down. The 2026 letter referenced both the main repository and running instances.
The update indicates legal review determined continued distribution of the frontend code does not trigger immediate liability when no proprietary instances are operated. This contrasts with service closures at other scraping-adjacent projects that lacked equivalent AGPL constraints or legal consultation. Operational continuity now depends on individual instance administrators relocating infrastructure.
Instance operators must next monitor X's enforcement actions against remaining domains and prepare DNS or hosting changes within the next 60 days to sustain availability above 80 percent uptime.
Nitter maintainers: At least 40 percent of public instances remain reachable 45 days after the commit date.
Sources (3)
- [1]Primary Source(https://github.com/zedeus/nitter/commit/1428b4c2b4246f92a7e5b2673438e5fb39fcc4a3)
- [2]Supporting Source(https://github.com/zedeus/nitter)
- [3]Supporting Source(https://github.com/iv-org/invidious)