←back to thread

151 points zdw | 10 comments | | HN request time: 1.001s | source | bottom
1. brailsafe ◴[] No.42153153[source]
Is there more to the thread or just this one tweet/X thing? Response times notoriously suck on MacBooks, it would be nice to see that remedied, anecdotally it doesn't seem like that's happened yet.

Edit: Nevermind, same tweet seems to have been quoted across a bunch of different other news sites. Apparently Blur Busters claims an improvement, I'll try it out and see how it is in some other contexts.

replies(1): >>42153226 #
2. anonym29 ◴[] No.42153226[source]
If you're not logged in to Xitter, navigating to a Xeet allows you to view the Xeet, but not the Xomments. Fortunately, there are open-source, self-hostable, privacy-preserving front-ends for Xitter, such as Nitter.

If setting it up yourself is too much work, you can use other public instances. One such instance is called xcancel. Load the Xeet as normal, then simply append "cancel" to the domain name before the period in your URL bar and hit enter :)

replies(3): >>42153348 #>>42153466 #>>42169871 #
3. bsder ◴[] No.42153348[source]
I thought nitter shut down because of the Xitter api changes.
replies(1): >>42153529 #
4. nicce ◴[] No.42153529{3}[source]
There were some workarounds, most buried in here: https://github.com/zedeus/nitter/issues/983
replies(1): >>42153620 #
5. chatmasta ◴[] No.42153620{4}[source]
No need for workarounds. Only the flagship nitter.net was blocked. Nitter is an open source project and maintains a list of working instances on its wiki: https://github.com/zedeus/nitter/wiki/Instances
replies(2): >>42153635 #>>42154866 #
6. ◴[] No.42153635{5}[source]
7. KTibow ◴[] No.42154866{5}[source]
I remember hearing something like "the way Nitter worked, guest accounts, was shut down and the 3 instances that remain work by using selfbotting" a while ago, it's logical although I haven't verified it
replies(1): >>42161701 #
8. chatmasta ◴[] No.42161701{6}[source]
What’s selfbotting? Based on the name it sounds like something that requires me to surrender my own authentication token to some automation service… but that’s definitely not the case for these alternative Nitter frontends.

I’m not sure how Twitter ultimately blocked them. It would be pretty embarassing (for Twitter) if it were a simple IP block of the Nitter.net servers, but that doesn’t seem too out of whack with Musk’s history of litigating bot behavior…

9. solarkraft ◴[] No.42169871[source]
In the context of a boycott, using/promoting Nitter is at best neutral - you’re not directly engaging with the most hostile parts of the site, but still engaging with it and making it easier for others to do so, unnecessarily promoting the idea of X being a good platform to post on.

I suggest not making any effort to use the site - rather just ask people to primarily share content from X by copying rather than linking. This removes the need to interact with it both for yourself and (more importantly) for others.

replies(1): >>42170744 #
10. brailsafe ◴[] No.42170744{3}[source]
> In the context of a boycott, using/promoting Nitter is at best neutral

I don't think that context was established, at least not in my comment, but I do agree with your second suggestion.