[Dunedan]

For me, an occasional reader without a Twitter account, the experience became much worse in the past decade. That's because Twitter switched of RSS feeds and when opening links to individual tweets nowadays there is this ubiquitous "Something Went Wrong, Try Again" on first page load.

[pests]

If I'm not mistaken that "Something Went Wrong" is their web API keys being throttled...

[heleninboodler]

If this happens to a client attempting to load a single page in isolation (which it does, a lot), you are a failed web site. They may be a very successful mobile app, but as a website, they've failed miserably.

[ikt]

I get this a lot and just assumed it was because I'm using a VPN.

[inapis]

I get this a lot if i’n using a VPN or an ad blocker like pi-hole.

[clarry]

I get that every single time unless I'm in private browsing mode. Clearing cookies and local storage makes no difference..

sigh

[dannyw]

It's absolutely absurd that this happens for a site as big as Twitter.

[rakoo]

I use nitter.net as an alternative frontend, it's better in every way

[djsumdog]

I love nitter and threadreaderapp. They make reading Tweets tolerable. The stock UI is just a confusing cluster fuck of Web 5.0 bloated webpacked Javascript bullshit.

[rakoo]

There is absolutely nothing the original UI offers that I want, it's all bloated all I want is the content. Unfortunately when I'm looking at a tweet I want to see the whole conversation with replies and such, but nitter doesn't show it, only some of the threads that start at the given tweet, so if I want to read it all I have to click everywhere and open 10 tabs. I wish there was a frontend that loaded the whole conversation in one go, the way HN or old reddit do