DevOps / SRE / Platform · 26.08.2026, 21:17 UTC
X sent Nitter a cease-and-desist. Then it went after the source code.
| Schweregrad | info |
|---|---|
| Kategorie | DevOps / SRE / Platform |
| Quelle | The New Stack ↗ |
| Veröffentlicht | 26.08.2026 UTC |
Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.
When Elon Musk’s X sent cease-and-desist letters demanding that Nitter — an open-source alternative front end for the social media platform — permanently shut down its instances and remove the project’s source code repository, it went after the code itself.
While Nitter.net was the project’s main public instance, other developers can run their own versions because the code is open source. So taking Nitter.net offline doesn’t really eliminate Nitter, because its code can be forked and used to run independent instances, including services such as XCancel. X’s demand for the repository goes further.
Open source meets platform control
Open source gives developers control over Nitter’s code, but not the platform it relies on. X still controls access to its service, and its latest move shows how that control can extend beyond just changing an API.
Open source gives developers control over Nitter’s code, but not the platform it relies on.
Nitter used to let people read public X posts without an account, but that stopped working in 2024 after X shut off the guest access the project relied on, taking Nitter.net offline. Nitter later found a way back by using real X accounts to access posts, according to the project’s GitHub repository.
That got Nitter back online, but it also meant relying on X accounts to keep it running. X controlled those accounts and could change the rules around them at any time. That doesn’t necessarily put someone who simply downloads or forks Nitter’s code in the same position, since doing so alone doesn’t mean they’ve agreed to X’s terms.
X’s …