So I had a really fun day writing up about Twitter trying to DDOS itself. I didn't expect it to blow up the way it did here, but even more amusing is that someone took a screenshot of that post and cross-posted it to Twitter and now that post is blowing up on Twitter too!

Poor Twitter. Can't catch a break. It's down and even the holdouts want their turn to give it a good kick.

Update: I have to add a screenshot of that screenshot because someone just reminded me that most people can't view the tweet unless they have a Twitter account to login to. It's ironic of me to forget because that's how today's circus got started.

It also shows how a seemingly innocent change like this can snowball into an avalanche of unintended consequences.

Anyway, 4500 retweets later and the party continues.

#selfDDOS #TwitterDown

https://twitter.com/Esqueer_/status/1675217212951461890

@sysop408 a friend there shared a screenshot of your write up. Kudos! Since then, I found this article which credits you with the find. Appreciate people that know their way around the code. Apparently Elon doesn’t. He should let experienced software engineers handle it.

Lesson to businesses relying on Twitter for anything - Don’t!

https://waxy.org/2023/07/twitter-bug-causes-self-ddos-possibly-causing-elon-musks-emergency-blocks-and-rate-limits-its-amateur-hour/

Twitter bug causes self-DDOS tied to Elon Musk's emergency blocks and rate limits: "It's amateur hour" - Waxy.org

An "amateur hour" Javascript bug is self-DDOSing Twitter, sending infinite requests from users related to — or possibly even causing — Elon Musk's "temporary emergency measures" to stop web scraping.

Waxy.org