Seemed worth a new post, now that they actually killed it today :(
Is there any frontend still standing?
zImPatrick · 2026-08-28 17:35:46 UTC
Nitter itself is still fine, there are like 2 public-ish instances I‘m aware of but I think people should go out and host some in more private communities/run one over Tor or something
rvz · 2026-08-28 16:48:31 UTC
This was obviously going to happen once Nitter got an immediate C&D.
It just means that it will happen to these alternatives as well and the lawyers have all the money from X Corp to do just that.
These open source projects circumventing X for free, unfortunately have zero chance in fighting these legal takedowns.
flotzam · 2026-08-28 16:59:57 UTC
Hoping we'll see more resilient development/hosting emerge
toomuchtodo · 2026-08-28 17:08:14 UTC
Probably the best use case for onion routing and IPFS. Each X URL gets a content addressable IPFS URL, served via an onion site that should be hard to take down.
Browser->Tor Onion site->IPFS as storage system pull through cache->X
flotzam · 2026-08-28 17:33:50 UTC
Or just a .onion for the frontend and code forge + another server at some clearnet domain proxying it (until taken down and replaced with the new one) would probably work fine. The hidden service can even terminate TLS with a valid cert for the clearnet domain.
toomuchtodo · 2026-08-28 18:16:08 UTC
True, I suggested IPFS as an hidden content addressable, globally distributed caching proxy and persistent object store. Run it from outside the reach of the US legal framework, like private/shadow libraries/archives.
Comments
https://news.ycombinator.com/item?id=49449576
Is there any frontend still standing?
It just means that it will happen to these alternatives as well and the lawyers have all the money from X Corp to do just that.
These open source projects circumventing X for free, unfortunately have zero chance in fighting these legal takedowns.
Browser->Tor Onion site->IPFS as storage system pull through cache->X
Distributed web adjacent.
https://getdweb.net/