> HN submissions are usually long-form content, so it's rare to see X links anyway.
There are, at minimum, tens of Twitter links that I see daily which make it to the first couple of pages of the site. A lot of them are AI-related content, which seems to be popular there.
> And in case an X submission is genuinely interesting, it won't be hard to access or infer the content from the comments or other sources.
I don’t want to have to do this. I think we should just disallow Twitter links for posts.
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
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.
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 (as you could consider it an archive of X, with public access when available).
Another idea I recently had was extending Karakeep (https://github.com/karakeep-app/), which has robust archiving capabilities today, to enable announcing archived URLs via a DHT and serving the archive bundle as a torrent (similar to how the Internet Archive creates a torrent file for each item). With some work, it would be the equivalent of a distributed Wayback Machine, with each instance able to act as both scraper and server. With a browser extension that could query this DHT, you could retrieve an archived version of any URL that has been archived by cherry picking from the swarm (each URL becomes a magnet torrent URL, very similar to IPFS, but with less bootstrapping required imho).
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
From HN's PoV, the issue is that there aren't well-known workarounds which can be used for X.com / Twitter.com submissions. HN's principle concern is more that any discussion on such posts will largely revolve around the regwall / paywall, which doesn't advance HN's own prime directive: <https://news.ycombinator.com/item?id=27901918>
I've emailed HN's mods requesting Twitter/X links be site-banned as hard-paywalled, given that Nitter and XCancel had also just received C&Ds (<https://news.ycombinator.com/item?id=49437283>).
Not good enough. Creating an account still leads to the "Your account was suspended for reasons, now you gotta dox yourself" dance. See previous discussion: https://news.ycombinator.com/item?id=49442907
reply