I have seen similar bugs in the systems I oversee because network libraries love to retry requests without sane limitations by default. But I never saw them make our rate limiters sweat. It's slightly more annoying when they hit an API which actually does some expensive work before returning an error but that's why we have rate limits on all public endpoints.
I also guess that the webapp is the least of Twitters traffic and the native apps probably don't have this problem.
Seems like either my quota reset or they changed the policy because I’m able to access the site again.
[1] "Now to 10k, 1k & 0.5k" (in reference to rate limits which were originally 6K 0.6K and 0.3K)
And another tweet that confirms disabling anonymous access was an emergency measure: https://twitter.com/elonmusk/status/1674942336583757825
> This will be unlocked shortly. Per my earlier post, drastic & immediate action was necessary due to EXTREME levels of data scraping.
> Almost every company doing AI, from startups to some of the biggest corporations on Earth, was scraping vast amounts of data.
> It is rather galling to have to bring large numbers of servers online on an emergency basis just to facilitate some AI startup’s outrageous valuation.