|
|
|
|
|
by the42thdoctor
1086 days ago
|
|
I think he was trying to say that the Frontend of the Twitter timeline is not aware of the new request limit, and when that limit is reached it just retries the request, as it would in a normal network error, and keeps in retrying resulting on DDOS. But I don't believe on that because Twitter is a billion dollar company and that kind of mistake is dumb. So idk. |
|
This sort of mistake is very common especially when a product is going through a period of change, so it seems very believable to me that recent rate limiting features (or older features that have not been used in a long time or maybe ever) on the backend hadn't been adequately tested to make sure there are no unforeseen side-effects on the front-end when they are activated under pressure.