Twitter Is DDOSing Itself
sfba.social
Twitter Is DDOSing Itself
1–10 of 1001 posts
Re: Twitter Is DDOSing Itself
#2I find it hilarious Mastodon is more stable than one-instanced Twitter run by some madness tech-maniac.
Re: Twitter Is DDOSing Itself
#3Archived: https://archive.ph/u5kNK
Re: Twitter Is DDOSing Itself
#4Could this be the reason for the rate limiting? Elon thinks the server usage is
scrapers when in reality it's just bad code causing a self DDOS?
Re: Twitter Is DDOSing Itself
#5> Twitter is firing off about 10 requests a second to itself to try and fetch content that never arrives because Elon's latest genius innovation is to block people from being able to read Twitter without logging in.
It seems an outlandish claim, but then again Muskified Twitter has previous form for this kind of thing with that time when they self-derailed by locking themselves out of their own api, right?[1]
Re: Twitter Is DDOSing Itself
#6I find it hilarious Mastodon is more stable than one-instanced Twitter run by some madness tech-maniac.
Mastodon has had its issues, both globally and for specific instances.
Sidekiq falling over is a big one. See: https://docs.joinmastodon.org/admin/scaling/> and https://nora.codes/post/scaling-mastodon-in-the-face-of-an-e...>
(I have to email my own admin every few months to ckeck if things are OK.)
And during the October Revolution as hoardes arrived from birdland, things got ssssslllloooowwww globally.
Worked out eventually, but it took a bit.
Individual instances also tend to run into scaling issues, with Jerry Bell's Infosec.Exchange coming to mind. (Mostly because Jerry's discussed this a bit.) And of course individual instances can be shut down or fail in various ways. I've migrated several times myself.
I will say that most of the time things seem fine, and it's exceptionally rare for there to be truly Fediverse-wide issues.
(I've been on Mastodon / the Fediverse since 2017, for the most part quite actively.)
Re: Twitter Is DDOSing Itself
#7This is interesting.
Judging from the screenshot, a huge amount of GET /TweetDetail is generated which triggers some rate limiting, as shown by the 429.
If this is indeed due to the recent decision to enforce authentication for all API calls, it means the curlprit may actually be the API gateway or something similar downstream.
Also, this behavior seem to never stop, which isn't what one would expect from an exponential backoff retry.
I don't claim to be a better engineer than the folks working at Twitter, but it is interesting to see something like this in the wild, all Musk-related considerations aside.
Re: Twitter Is DDOSing Itself
#8Bluesky feels like it’s buckling under the refugee crisis load
Re: Twitter Is DDOSing Itself
#9Now I’m really tempted to create a Twitter account and start reading. Maybe that’s 3D chess by design by the CTO to get people to sign up. /s
Re: Twitter Is DDOSing Itself
#10Keep in mind that Twitter engineers are under extreme pressure, knowing that their H1B visas are at stake, to implement Elon’s whims as quickly as possible on systems they’re unfamiliar with. I doubt many of us would perform better in their situation.