Elon Musk's X has 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, according to a report published by The New Stack. The legal action goes beyond taking down Nitter.net, the project's main public instance, by targeting the code itself. Because Nitter is open source, developers can fork the code and run independent versions, including services like XCancel, so eliminating the repository would go further than simply shutting down one website.
Nitter originally let users view public X posts without logging in, but that capability stopped functioning in 2024 after X disabled the guest access the project depended on, which took Nitter.net offline. The project later discovered a workaround by using actual X accounts to pull posts, according to its GitHub repository. This approach brought Nitter back online but created a new dependency on X accounts that the platform could control and restrict at any time. 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.
According to the cease-and-desist letter—first reported by TechCrunch—X claims Nitter violated its rules by scraping data and accessing accounts and session tokens, and accuses the project of "unlawful use and circumvention" of its API. X's lawyers also cited the Lanham Act and Section 33.02 of the Texas Penal Code, which deals with accessing computer systems without the owner's "effective consent." The report notes that breaking a platform's rules doesn't mean the law was broken, too. X reportedly says Nitter got around its API restrictions to access accounts and session tokens, but the question is whether those restrictions were protecting copyrighted material in the way Section 1201 of the Digital Millennium Copyright Act requires.
The situation echoes a 2020 case when GitHub removed the open-source YouTube-dl project following a Section 1201 complaint from the Recording Industry Association of America. GitHub later restored that repository and changed how it handles these complaints, adding technical and legal review before removing code when a circumvention claim isn't clear. For a Section 1201 complaint, the company must identify the copyrighted material being protected and explain how the code circumvents the technology controlling access to it, according to GitHub's guidelines for submitting circumvention claims. For now, the Nitter repository remains on GitHub, archived and read-only—the code can still be viewed and forked, even though Nitter's developer is no longer working on it. The precedent suggests platforms can pressure open-source projects not just by cutting off access, but by challenging whether the workarounds developers build to restore functionality cross legal lines around copyright protection. How GitHub interprets those lines will shape whether developers can maintain independent interfaces to platforms that don't want them.