They lowered some of the rate limits last night to the point where it was very easy to hit them. Seems like they kept doing that, but broke something, because my timeline says I exhausted my allocation of 900 hits to the API and I have to wait about a full day before I can try again.
I get a generic "Something went wrong" error on web* but with dev tools open I can see it's getting 429 Too Many Requests with responses that say "rate limit exceeded". The app might not have been coded to show a rate limit error, maybe.
*except search, which does actually pop up a message saying I'm rate limited.
I’ve only experienced somewhat minor bugs throughout the last eight months, including some that have always been there (what’s with the site’s inability to load Quote retweets?), but this has got to take the cake. Guess the “Twitter is doomed” narrative is into something.
11 comments
[ 4.4 ms ] story [ 38.4 ms ] thread*except search, which does actually pop up a message saying I'm rate limited.
After a few likes, retweets, and searches, it starts to slow down and finally shows the "Rate Limit exceeded" message.
They cannot start charging users for "fast-paced" browsing, adding that to Twitter Blue benefits.