TwitterWebViewer also no longer in operation, following a request from X Corp(twitterwebviewer.com) |
TwitterWebViewer also no longer in operation, following a request from X Corp(twitterwebviewer.com) |
I'm not any authority here, but I'd say, there's no need for a Reddit-moment to ban it entirely.
Though it wouldn't bother me either.
Directly linked single text posts are still publicly accessible last I checked, but it's a microblogging platform littered with spam.
HN submissions are usually long-form content, so it's rare to see X links anyway.
And comments obey the voting system, so who cares whether people link to X, LinkedIn, Facebook or whatever else.
Banning X in comments would require to ban the others as well, and I think the mods and users can handle by themselves what is relevant in that case.
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.
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.
“It's ok to post stories from sites with paywalls that have workarounds.“
There don’t appear to be workarounds for Twitter anymore.
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
Is there any frontend still standing?
Their comment history makes this clear.
<https://github.com/zedeus/nitter/issues/1442>
HN: <https://news.ycombinator.com/item?id=49437283>
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>
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).
Distributed web adjacent (https://getdweb.net/).