Hacker News Reader

Comment by ufo | Hacker News Reader

A high percentage of the time when I attempt to view a twitter page on mobile the spinner times out and just gives a "something went wrong" error. There is a Try Again button but clicking on it is futile, as it always goes back to "something went wrong" error after a second. The only thing that seems to work is to ask the browser to refresh the page, sometimes more than once.

Is this only happening to me? I always wondered what the hell is going on.

View on HN

Happens to me too all the time on mobile and boy is it infuriating. I either get the "something went wrong" or the "you're being rate-limited," neither of which make any sense for someone opening tweets every now and then inside other apps.

I assume it's because when you open tweets with in-app browsers etc. Twitter wants to make it a poor experience in order to get you to use their app instead. Same reason they have been gutting their API features and limiting API tokens for 3rd party apps for years now.

Happens to me every time. I think it is intentionally done if you are not logged in to discourage you from using Twitter.

This happens to me as well, but only on mobile. Maybe the result of some rate-limiting, combined with not being able to distinguish different mobile users on the same network? I also use ublock origin with Firefox mobile, fwiw.

Often when it happens refresh isn't even enough, I have to do a duplicate tab operation. I had that issue on mobile for a long time, now I have it on desktop too. O boy.

Happens to me a lot on desktop, especially when following an external link to a tweet. Like you say, refreshing the page fixes it. Also seen it on mobile from time to time. Expected they’d fix this before a wider rollout, it’s pretty common for me!

It's also happening to me but usually works on second try when resubmitting the url omitting the "mobile." subdomain

Reply on news.ycombinator.com