- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
It’s possible that the enforcement of a rate limit isn’t because of AI scraping, but rather because they failed to migrate before the June 30th deadline.
It’s possible that the enforcement of a rate limit isn’t because of AI scraping, but rather because they failed to migrate before the June 30th deadline.
Classic Elon playbook. Make wild statement in public to cover for a wild business decision which is the real result. “HAHA oh yea Twitter is down cuz of these limits I put in place, not the fact that one of our core cloud providers shut us off.”
“All the woke posts are causing network disruptions because their cancel culture leaks into the routers.”
There was a post earlier today, but the post limit implementation legitimately did take down Twitter.
In short, twitter ddosed it’s self by making 10 calls to its self every couple of time intervals (a minute or less) which would fail, refresh the UI and kick off even more self requests.
Ah the classic deploy to prod right before the weekend WCGW
What’s the worst that could happen?
Unpaid emergency overtime for all Twitter devs this weekend!
But it NEEDS to go out before the end of the quarter, there’s no way around it! /s