Molly Whitetwitter's self-ddos is worse with tweetdeck đź’€
this is the page after it's been open for a few minutes
it's just repeatedly retrying 404s lol
the successful calls are because the home timeline and DMs still seem to work. everything else is just the loading spinner
joël@molly0xfff if you need to use tweetdeck, you can have use the notifications-only column, these work for some magical reason.
Fahri Reza 🍉different microservice probably :D
zazaserty@molly0xfff As bad and pathetic as this is for Twitter, it will probably take way more for people to move away from it. And even if they do, they could migrate into another corporate platform.
Such is the way of the modern consumer.
Jack OvaltradePeople fail to understand that myspace didn't loose its user in one day. It just slowly degraded over years.
People started to slowly move to Facebook, then inciting their friends, then friends of friends joined, ...
*If* mastodon prevails over twitter, it won't happen overnight.
CentauriusCan we talk for a minute about those messages you are showing? Damn people are thirsty for crypto and out trying to "connect".
@Centaurius but Elon fixed the bot problem 🤷‍♀️
MostlyFinished@molly0xfff Why is it returning a 404 instead of a 429? Which in theory the client side code should have an error handler for. Someone needs to tell Twitter engineers that http status codes exist for a reason.
Edelruth, PBS Passport HolderI am sure someone would tell those engineers if Elong had not fired them all.
Sandbender@molly0xfff
What software is this? I'm trying to do these sorts of analyses, but I come from the silicon and can't for the life of me figure out what the good tools are.
What software is this? I'm trying to do these sorts of analyses, but I come from the silicon and can't for the life of me figure out what the good tools are.
Mynacol@sandbender @molly0xfff That's just the network tab in the Chrome developer options. Try hitting F12 in your favorite web browser.
Andrew Scagnelli-Townley@sandbender @molly0xfff looks like Chrome’s built-in developer tools, set to the “network” tab, which logs every in-/out-bound network request
The fact that they’re blindly firing retries instead of an exponential back-off is… not smart web engineering. And it’s a little strange they’re hitting a JSON endpoint, I thought they had a GraphQL setup to simplify/reduce over fetching/provide sitewide exponential backoff as a default.
jhannafin@sandbender @molly0xfff These are just the Chrome built-in dev tools. Hit F12 and poke around. Firefox has similar tools. They're very useful and quite informative.
Nathan A. Stine@molly0xfff don't walk away while your browser is on the website. You might accidentally help DDOS it!
PunnO)))@molly0xfff extremely hardcore engineering right here
botvolutionThat's interesting.
The big complaint has been that everyone was getting rate limited, which would be a 429
Merc@molly0xfff For the less tech savvy, 404 is not an error you retry.
Pretend you're calling someone on the phone.
429 is roughly "Hey Molly, call back later, I'm waiting for another call"
500 is when you just get some weird beeps when you call the number, something broke at the other end.
302 is "Jeff changed his number, you can reach him at 555-1212"
404 is "Sorry, wrong number. No Jeff here."
Retrying a 404 is like calling back after you're told you have a wrong number, just in case there's now a Jeff there -- and in this case, doing it as soon as you hang up, over and over.