Twitter Is DDOSing Itself • Hacker News Board

Re: Twitter Is DDOSing Itself

#91

Post by candiddevmike » Sat, Jul 01, 2023, 8:53 PM UTC

pronik wrote: post #80

brucethemoose2 wrote: post #28

Meanwhile, I can see this very Mastadon post with no login just fine. And the interface is not trying to assault me. It loads quick. ...Seems like a better product than Twitter for a public feed.

Early days of Twitter were just like that. Mastodon hasn't had the time to go to shit yet.

How could a decentralized thing go to shit?

Re: Twitter Is DDOSing Itself

#92

Post by candiddevmike » Sat, Jul 01, 2023, 8:54 PM UTC

amelius wrote: post #64

brucethemoose2 wrote: post #28

Meanwhile, I can see this very Mastadon post with no login just fine. And the interface is not trying to assault me. It loads quick. ...Seems like a better product than Twitter for a public feed.

I'm sure the loads are not comparable.

It's not crunching a bunch of analysis or ads in the background. I bet it scales wonderfully with maybe some kind of cache/CDN if necessary.

Re: Twitter Is DDOSing Itself

#93

Post by mbrz » Sat, Jul 01, 2023, 8:54 PM UTC

throwawat7832 wrote: post #79

mbrz wrote: post #70

Earlier quoted context omitted.

like this? https://imgur.com/Ru6ZlCK

over what period? I left my dev tools open since my original post (14 minutes) and and it looks like this, so 197 requests / 14 minutes = 14 requests per minutes, which is not a DDOS: https://imgur.com/8sxBAPt

right now im at around 150 per minute https://i.imgur.com/qjbsQU7.png

Re: Twitter Is DDOSing Itself

#94

Post by Macha » Sat, Jul 01, 2023, 8:54 PM UTC

pronik wrote: post #80

brucethemoose2 wrote: post #28

Meanwhile, I can see this very Mastadon post with no login just fine. And the interface is not trying to assault me. It loads quick. ...Seems like a better product than Twitter for a public feed.

Early days of Twitter were just like that. Mastodon hasn't had the time to go to shit yet.

The point of it is that it isn't a company but a standard, so if one instance owner goes crazy and patches ads in you can move to another (or your own) and keep your network

Re: Twitter Is DDOSing Itself

#95

Post by throwawat7832 » Sat, Jul 01, 2023, 8:55 PM UTC

summerlight wrote: post #83

throwawat7832 wrote: post #58

[flagged]

> Lest anyone doubt that Twitter was idiotic enough to release code that would cause a race condition and result in its own users executing a DDOS attack on it Given that this is a race condition bug as stated in the original post, it's unlikely something reproducible in a deterministic way. You could probably give it a little bit more attention before leaving this reply...

Has anyone managed to replicate it? If he's claiming it's DDOSing twitter it sounds like it should be happening for multiple users

Re: Twitter Is DDOSing Itself

#96

Post by cactusplant7374 » Sat, Jul 01, 2023, 8:55 PM UTC

amluto wrote: post #88

cactusplant7374 wrote: post #84

Earlier quoted context omitted.

Did Elon pay the AWS bill? That seems like a likely culprit. Twitter instances are being forcibly shutdown.

Twitter operates its own datacenters.

"Twitter and AWS signed a five-and-a-half-year contract in 2020, which AWS is not willing to renegotiate."

https://gritdaily.com/twitter-owes-aws-millions/

Re: Twitter Is DDOSing Itself

#97

Post by jtrip » Sat, Jul 01, 2023, 8:56 PM UTC

Pxtl wrote: post #11

jitl wrote: post #8

Bluesky feels like it’s buckling under the refugee crisis load

Mastodon.social is chugging along just fine

Meaning.. people prefer bluesky to mastodon?

Re: Twitter Is DDOSing Itself

#98

Post by throwawat7832 » Sat, Jul 01, 2023, 8:56 PM UTC

mbrz wrote: post #93

throwawat7832 wrote: post #79

Earlier quoted context omitted.

over what period? I left my dev tools open since my original post (14 minutes) and and it looks like this, so 197 requests / 14 minutes = 14 requests per minutes, which is not a DDOS: https://imgur.com/8sxBAPt

right now im at around 150 per minute https://i.imgur.com/qjbsQU7.png

Guess I take it back. I still hate seeing the mob mentality but maybe it's right.

Re: Twitter Is DDOSing Itself

#99

Post by Matthias247 » Sat, Jul 01, 2023, 8:57 PM UTC

oh_sigh wrote: post #52

Certainly not good, but not all GET requests are equal. If these are responded to cheaply, at the point of connection termination, then it might be the case that no one has bothered to clean it up yet.

Not exactly sure if that's what you recommend. But connection termination is not necessarily a good thing for DDOS mitigation. The reason is that the client might just retry immediatly - and it will do that using a new TLS connection. And the handshake for that connection has a huge cost. If you plan on disconnecting clients *after* a TLS connection had been established, you will also need to implement TLS handshake rate and connection limiting. That's possible, but I've only seen a tiny amount of services every implementing it.

Re: Twitter Is DDOSing Itself

#100

Post by WJW » Sat, Jul 01, 2023, 9:00 PM UTC

hinata08 wrote: post #74

amelius wrote: post #64

Earlier quoted context omitted.

I'm sure the loads are not comparable.

It withstands being one of the first link on HN, and it still loads comfortably. For a personal website, that's a great performance.

HN traffic is not nearly the DDOS people make it out to be. I made it to spot #2 once and that was a few dozen hits per second at most. Maybe not something to serve with wordpress from a raspberry pi, but hardly apocalyptic levels of traffic.