XCancel comes back online after X's cease-and-desist

Why it matters

XCancel's return shows how open-source maintainers can survive a platform crackdown, while exposing the legal and operational risk carried by each public instance operator.

The operator behind XCancel has brought the privacy-oriented X viewer back online less than two weeks after a cease-and-desist from X Corp. pushed XCancel and the open-source project beneath it offline.

XCancel's home page was serving its search interface on September 6th, while its About page identified the running build as version 2026.09.06-ecdfc92. The pages establish that the public instance is reachable again. They do not establish whether every profile, search, timeline and RSS function has returned.

The restart followed a parallel decision by Nitter's maintainer, who uses the name Zedeus on GitHub. In a repository update, Zedeus wrote that the project would continue after receiving legal advice. The same commit was titled "Update README - Nitter lives."

That wording matters because XCancel and Nitter have different operators. XCancel runs an instance of Nitter's software, and XCancel's About page explicitly says donations to the two projects go to separate people. Zedeus maintains the upstream code; XCancel's operator handles the servers, accounts and day-to-day work required to keep this particular public viewer available.

A maintainer-run service facing a platform's lawyers

XCancel is closer to a public utility maintained by an independent operator than a conventional startup. It has no announced venture round, paid subscription or advertising business. Its operating model relies on donations routed through Liberapay, Ko-fi and cryptocurrency addresses.

The person running XCancel solicits that support under the name "yewtube," through a Ko-fi page shared with Yewtu.be and searx.be. That page says donations help maintain the servers and accounts needed to keep XCancel, Yewtu.be and searx.be operating.

That is an unusually direct description of the maintenance burden behind an unofficial front end. XCancel has to absorb the cost and operational risk of staying connected to a platform whose owner wants users inside its own interface.

The upstream Nitter repository describes the software as a free, open-source front end for viewing public X content without JavaScript, ads or an X login. Requests pass through the instance's backend rather than sending the visitor's browser directly to X. Nitter claims this arrangement prevents X from receiving the visitor's IP address or JavaScript fingerprint. Those privacy claims have not been independently audited.

The repository had about 14,200 GitHub stars and 1,300 forks on September 6th. Those figures show developer interest in Nitter's approach, although they say nothing about XCancel's traffic or number of users.

X moved from technical blocking to legal pressure

X has spent years tightening access to public posts outside its own apps and website. Nitter's flagship service temporarily went dark in 2024 after changes to X's guest-account access forced operators to connect real X accounts to their instances.

The August action raised the stakes. X sent cease-and-desist letters on August 24th demanding permanent takedowns of Nitter instances and the project's repository, according to the notice subsequently published in Nitter's README.

TechCrunch reported that it reviewed X's letter, which accused Nitter of scraping data and demanded that the project and its instances be taken down. The report also identified legal claims made by X in the dispute.

Contemporaneous reporting identified XCancel as one of the services that received a demand and went offline.

XCancel's return on September 6th shows that the letters did not produce the permanent disappearance X demanded. The Nitter repository also remains public, with installation instructions for operators who want to run their own instances.

The code can continue; each operator still carries the risk

Open-source distribution makes Nitter difficult to erase through a demand aimed at one maintainer. The repository's AGPL-3.0 license permits others to inspect, modify and deploy the software under its terms. A public instance remains much easier to identify and pressure because it needs a domain, hosting infrastructure and working access to X.

XCancel's setup captures that tension. The software can be copied, while the operating work stays concentrated with a person paying for servers, maintaining X accounts and handling legal correspondence. Donations may cover infrastructure. They do not remove the dependency on X's unofficial access methods or the legal exposure created by offering the service publicly.

The September 6th return is consequently a practical act by a maintainer rather than a resolution of the dispute. XCancel is reachable, Nitter's code is still available, and Zedeus says development will continue after legal advice. The same technical and legal dependencies that forced the August shutdown remain embedded in the product.

For XCancel's operator, keeping the service alive means continuing to make a small, donation-supported system withstand decisions made by one of the world's largest social platforms. On September 6th, the operator put it back on the public web.