On August 24, X Corp. sent cease-and-desist letters to the maintainers of Nitter, the open-source front-end that lets people read tweets without logging in, without JavaScript, and without being tracked. The letters cited the Texas Harmful Access by Computer Act and the Lanham Act, demanded the takedown of every public instance and the project’s repository by 5 p.m. Eastern the next day, and succeeded in taking nitter.net offline. The developer behind the project, who goes by Zedeus, told TechCrunch he was seeking legal advice and wouldn’t comment further.

Two weeks later, the predictable thing happened: there are now more working Nitter instances than before the takedown. The Hacker News thread celebrating this fact has hundreds of comments. The lesson being drawn, loudly, is that you can’t kill an open-source project with a lawyer — the Streisand effect, the hydra, the internet routes around censorship.

That’s the comfortable take. It’s also the wrong one.

The Takedown Was a Confession, Not a Strategy

X’s legal team didn’t wake up on August 24 and decide to pick a fight with a niche privacy tool out of spite. They did it because Nitter had become the only way a meaningful number of people were willing to read the platform at all. The project’s own documentation boasted that it was roughly 15 times lighter than twitter.com — no ads, no algorithmic feed, no login wall, no session tokens phoning home. For seven years, that was enough to sustain a small but stubborn user base.

Then something changed. X’s product decisions — the login walls, the rate limits, the aggressive data collection, the degradation of the logged-out experience — pushed more and more casual readers toward the workaround. The takedown wasn’t a preemptive strike. It was an admission that the official product had lost the competition for its own content.

A developer who maintains one of the surviving instances put it plainly in a Slack message this week: “We didn’t build this because we hate X. We built it because reading tweets on X became unbearable. The C&D just told us we were right.”

That’s the part the victory-lap crowd misses. The proliferation of instances isn’t a triumph of anarchic tech culture over corporate power. It’s a market signal. When a free, volunteer-maintained tool with no business model and no marketing budget becomes the preferred way to consume your product, you don’t have a piracy problem. You have a product problem.

The Lanham Act Citation Is the Tell

Buried in the legal filing is a detail worth pausing on. X cited the Lanham Act — 15 U.S.C. §§ 1114 and 1125 — which is trademark law. The argument, presumably, is that Nitter instances confuse consumers or dilute the X brand. That’s a remarkable claim to make about a tool whose entire purpose is to display X’s own content without the surveillance apparatus.

Think about what that implies. X is arguing, in effect, that the experience of reading tweets is so bound up with the brand that a cleaner, faster, less invasive version of it constitutes consumer confusion. The lawyers are saying: the tracking, the ads, the login wall — that’s not overhead, that’s the product. Strip it away and you’re not pirating the content; you’re counterfeiting the brand.

That’s a coherent legal strategy. It’s also a devastating self-indictment. If the brand is inseparable from the friction, then the friction is the point. And if the friction is the point, then every Nitter instance is a reminder that the friction is optional.

What the Instance Count Actually Measures

The Hacker News thread treats the instance count as a scoreboard: open source 1, X Corp 0. But the number of working instances isn’t a measure of resilience. It’s a measure of unmet demand. Each new instance is a small business owner in suburban Ohio deciding that the official product is bad enough to justify the legal risk of running a mirror. Each one is a user who would rather configure a third-party front-end than log in.

That demand didn’t appear on August 24. It’s been building for years, every time X made the logged-out experience worse. The cease-and-desist didn’t create the hydra; it just made the hydra visible.

The uncomfortable question for X’s leadership isn’t whether the takedown will work. It’s whether the takedown was ever the right tool. You can send lawyers after every instance, every fork, every mirror. You can cite the Texas Harmful Access by Computer Act until the cows come home. But you can’t litigate your way out of a product that people are actively working to avoid.

The instances will keep multiplying. Not because the internet is ungovernable, but because X has spent years making its own platform the worst way to read it. The takedown didn’t fail. It just revealed what was already true.

Sources