the 4,000-character tweet feature, launched for paying subscribers this morning, overloaded something on the backend. they had automated protections in place which shed load.... by enforcing a rate limit of 0.
the 4,000-character tweet feature, launched for paying subscribers this morning, overloaded something on the backend. they had automated protections in place which shed load.... by enforcing a rate limit of 0.
My guess is that they messed with the bit of code that allows an app with multiple users to have a rate limit for each user individually, and now every user of say tweetdeck is competing for bandwidth with every other user of tweetdeck, and same for the web view, but every account that posts a picture of a moth every hour or whatever already had its own API key and is fine.
...but then I hadn't heard about this 4000 character limit