2 ms·
Yeah, what is the deal with that, anyway? Twitter is constantly giving me the "something went wrong" message or telling me that I'm being rate-limited even thou
by trav4225 6y ago
Yeah, what is the deal with that, anyway? Twitter is constantly giving me the "something went wrong" message or telling me that I'm being rate-limited even though I only hit the site about 10 times a week.
- tgsovlerkhgsel 6y agoMy guess is their bot/scraper detection not liking anything that's not a 100% standard, extension-free browser. Although I've heard that even people without privacy extensions are getting hit by it, so it may just be a super aggressive bot detection that's randomly hitting everyone or some other bug that Twitter doesn't care because it presumably a) doesn't affect logged in users b) non-logged-in users who go there really want/need to see something (e.g. whether the US president is about to deport them) so they will put up with it and reload.
- jen20 6y agoI see this constantly, but primarily when I click a link to Twitter in an app other than a browser (e.g. Slack). It's been years now, so I'm 100% sure Twitter must know about the issue and have just chosen to not care.
- nullc 6y agoGo to about:debugging#workers and remove all "service workers" for twitter (these are persistent background tasks that, among other things, can act as proxy servers for requests on pages). This will resolve the problem, at least temporarily. You can disable service workers entirely by setting about:config dom.serviceWorkers.enabled to false.