zlacker

[return to "Twitter Is DDOSing Itself"]
1. lamont+yx[view] [source] 2023-07-01 21:16:01
>>ZacnyL+(OP)
I think we're about at the point where the people who predicted chaos at twitter after Elon basically fired most of the experienced engineers have been proven correct. The duct tape is all coming apart at the seams now.

It isn't quite as decisive as a submarine imploding, and ceasing to exist, but it has turned into a brightly burning tirefire.

◧◩
2. termin+KD[view] [source] 2023-07-01 21:56:06
>>lamont+yx
right? it's a shame hacker news doesn't let you reply to old comments, there's a few threads I'd like to follow up on from people who refused to believe Elon was destroying twitter
◧◩◪
3. Maraza+nE[view] [source] 2023-07-01 22:00:31
>>termin+KD
I think I had someone do the old sarcastic "remind me of this in one year" under one of my posts predicting technical doom for Twitter.

Definitely a good one to revisit.

◧◩◪◨
4. dcunit+Uta[view] [source] 2023-07-04 22:51:50
>>Maraza+nE
Yeh, except you're completely wrong. I tried to point this out below. It's not even a DDoS, it's fake news.

>>36561808

it's a 429 error, so the developer who posted this is an idiot. they're not even wrong. the 429 doesn't even touch twitter's infrastructure. the HTTPS TLS terminates at a Google VM, which gets relayed depending on the VIP used to hit it, but the traffic never gets past that Google VM. This is literally /HOW/ companies deal with DDOS.

https://blog.twitter.com/engineering/en_us/topics/infrastruc...

it's unbelievable that my median salary for the past decade is $3,000 after several years of "Startup" followed by "How to Start a Reboot of My Life"

[go to top]