4 ms·

Twitter's web version is an abomination. Every time you click on a link to read a tweet, you get an error. Every time. You need to force a refresh to get the

• userbinator 6y ago
  What's even worse is that the much better static-page "mobile" version which I've been using (mobile.twitter.com), and you can only get to it if you set your UA to an older browser, now has this ominous "warning": "This is the legacy version of twitter.com. We will be shutting it down on 15 December 2020." It's deeply disturbing that if they go full-SPA like YouTube did, it seems not a single person working there realises the insanity of somehow needing so much software (and hardware) just to read 140-character long microblogposts, something that would've been possible with hardware and software from 30 years ago. If you look at their minimum browser requirements, then look at the minimum OS requirements from the browser, and go back to hardware requirements from that, you'll probably end up with something that seems ridiculously overpowered for the task, yet with that "minimum supported" system the site will still be slow as molasses and worse than the static page. Seriously, what the fuck!?
• account42 6y ago
  Go to about:serviceworkers (for Firefox, other browsers might have it elsewhere) and remove anything related to twitter - or better yet disable service workers entirely. Not saying that this is acceptable, just providing a workaround.