TwitterWebViewer also no longer in operation, following a request from X Corp(twitterwebviewer.com)

10 pointsby flotzam2 hours ago3 comments

Kim_Bruning5 minutes ago
For HN, does that mean we should no longer be using X links, since most can't view them?
rvz2 hours ago
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.
- flotzam2 hours ago
  Hoping we'll see more resilient development/hosting emerge
  - toomuchtodo2 hours ago
    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
    flotzaman hour ago
    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.
    toomuchtodo26 minutes ago
    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.
    Distributed web adjacent.
    https://getdweb.net/
ChrisArchitect2 hours ago
Related discussion and predictions (2 days ago):
https://news.ycombinator.com/item?id=49449576
- flotzam2 hours ago
  Seemed worth a new post, now that they actually killed it today :(
  Is there any frontend still standing?
  - zImPatrickan hour ago
    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