I clicked a link. The Nitter page that had once let you skim X without an account greeted me with a cold legal notice. For a beat I felt like someone quietly closed a door I used to slip through.
I want to be blunt: if you enjoy peeking at X without feeding the algorithm, this is bad news. You and I have used forks, instances, and browser tricks to dodge login walls for years. Now the project’s maintainers have announced they’re pausing work after receiving legal pressure from X Corp., and that pause feels a lot heavier than a timeout.
“Cease and desist”
On 24 August 2026 cease and desist letters have been sent by X Corp. demanding a permanent takedown of Nitter instances and the project’s repository.
nitter.net is offline and development has stopped for the time being. I’m seeking legal advice and won’t be commenting further on the specifics for now.
Thank you to everyone who used, hosted, packaged, donated and contributed to Nitter over the past seven years.”
On my timeline: a TechCrunch link claiming it read one of X’s letters.
TechCrunch reports that one of the letters accuses Nitter of “unlawful use and circumvention of X’s Application Programming Interface (API) and associated data,” and cites the Texas Harmful Access by Computer Act and the Lanham Act. I read that and felt the immediate legal weight — not a negotiation, but a demand. You can picture how maintainers who run small, distributed instances might react: legal bills, risk of seizures, and volunteers suddenly needing counsel.
What happened to Nitter?
Nitter’s main public instance, nitter.net, is offline and the core repo shows a terse notice. The maintainers say they’ve stopped development while they seek legal advice. Other instances still flicker and a few non-U.S. hosts are reportedly holding pages for now, but the network that made Nitter resilient is thinner than it was last week.
A colleague in Europe messaged to say a few mirrors still work.
That’s important because Nitter is open source — copies can live anywhere. But being distributed isn’t a shield against legal pressure. I’ve watched projects that felt bulletproof dissolve when a major service decided to enforce its terms; this feels similar, like a bunker losing power, and you start counting how many doors need locking.
Is Nitter legal?
Legal answers live in gray. X’s letter, as reported, frames the project’s actions as circumvention of an API and violations of certain statutes. I can’t give you legal advice, but the maintainers’ pause suggests they don’t want to risk a test case. If you host or mirror an instance, you’re one phone call away from a different risk profile than a casual reader.
I opened GitHub and Reddit to feel the atmosphere of the moment.
The project’s GitHub carries the same short notice; Reddit threads show users split between panic and stoicism. ArsTechnica and others flagged that Nitter has survived scrapes and API cutoffs before — notably when Twitter altered access in 2024 — but survival then required volunteers willing to patch and rehost. This time X Corp. went legal, and legal letters are harder to patch than code.
Here are the platforms and names in the ring: X (formerly Twitter), Nitter’s repo on GitHub, journalists at TechCrunch and ArsTechnica, and Reddit users keeping tabs on mirrors. If you follow any of those feeds, you’ve already started forming an opinion on what’s legitimate and what isn’t.
Can I still read X posts without an account?
Right now: sometimes. Some Nitter instances outside the U.S. are still serving content; other third-party front ends may temporarily work. But the odds feel lower than they did yesterday. If you rely on scraping tools or third-party readers, expect interruptions and potentially permanent shutdowns as legal pressure spreads.
I’ll be honest: I root for small projects that make the web less gated and more usable. At the same time, I’ve watched maintainers fold when the legal cost exceeds volunteer goodwill. This is not just a tech problem; it’s a money-and-power problem.
If you care, here are practical moves I’d recommend you consider: follow alternate instances rather than a single URL; mirror public archives you legally can; and support projects that publish transparency reports or legal defense funds. That is how distributed projects buy time.
Two small metaphors will help you remember the stakes: one is that a project under legal pressure behaves like a bunker losing power — the structure is intact, but every essential system starts to fail. The other is that one aggressive legal push can be the loose thread that unravels a sweater; volunteer networks are fragile in different ways than corporate ones.
I want to know how you feel about reading X without logging in. Do you think volunteer tools should be protected even when they irritate platform owners, or is this a case of platforms defending their turf at all costs?