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.
It‘s pretty clear to me this guy knows nothing other than “how to throw money at intelligent people to make them make more money”, but with Twitter he somehow didn‘t do that. Instead he went the opposite way, to not pay bills and fire the intelligent people. I can only surmise, that this is an effort to destroy Twitter, maybe it was a thorn in some countries side?
Somehow even this position is giving the dude too much credit.
Yeah I feel you, it‘s like the “rich person at a carnival” parable:
Entrepreneurship is like one of those carnival games where you throw darts or something.
Middle class kids can afford one throw. Most miss. A few hit the target and get a small prize. A very few hit the center bullseye and get a bigger prize. Rags to riches! The American Dream lives on.
Rich kids can afford many throws. If they want to, they can try over and over and over again until they hit something and feel good about themselves. Some keep going until they hit the center bullseye, then they give speeches or write blog posts about “meritocracy” and the salutary effects of hard work.
Poor kids aren’t visiting the carnival. They’re the ones working it.Maybe this is just a miss. I tend to see plans or conspiracy sometimes, when it could just be incompetence.
Last week a billionaire imploded the sub he was piloting because he thought he could outsmart the laws of physics.
Never being told “no” makes a person stupid.
He thought that Twitter’s appeal to the best developers is the same as SpaceX’s and Tesla’s on their own tech areas, but to anyone else it’s pretty obvious that Twitter isn’t that special.
This is just too funny:
It’s currently unclear when this bug went into production, or how much it’s actually impacting their traffic, so it’s hard to determine whether this bug inadvertently inspired Twitter to block unregistered access and add rate limits, or if the bug was triggered by the rollout of those changes.
Do they not have version control? How can they not realise when the code snippet got added to the source code!?
Twitter might know but we don’t and that’s what the article is saying.
Could be a poison pill by a disgruntled ex employee. So maybe they’ve obfuscated the addition of the code snippet across several commits hidden inside legitimate commits.
maybe the elongated moskowrat coded it himself.
“temporary emergency measures”
More like, desperate emergency measures
Thanks guys, that was a really good laugh to start the day with. Business genius doing business genius things again.
in the elongated moskowrat’s case “genius” is short for “genuine ass”
Lol. I’ve only been following this from a distance because I don’t have any real interest in Birdsite anymore, but hadn’t appreciated that they themselves may have caused the increase in API requests that cause them to introduce rate limits. That’s hilarious.
