Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Twitter Is DDOSing Itself

sfba.social

Post reply on HN
Print view View original

71–80 of 1001 posts

Re: Twitter Is DDOSing Itself

#71

Post by bheadmaster »

arter4 wrote: post #7

This 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 exponent…

> 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.

The way I understand it, DDoS is not caused by enforced authentication - enforced authentication is just a temporary measure against DDoS.

Re: Twitter Is DDOSing Itself

#72

Post by teawrecks »

bboygravity wrote: post #55
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.

Most of the rest of the world doesn't agree.

Also most of the rest of the world doesn't use Twitter (I'm seeing about 240M total users?). The ones that do use Twitter do so because of a significant amount of money going into marketing Twitter's platform.

Conversely, relatively nothing goes into pushing people to use mastodon. It can only take off if it really does prove, not just useful, but more useful than a centralized version that's got money behind it.

Re: Twitter Is DDOSing Itself

#74

Post by hinata08 »

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 withstands being one of the first link on HN, and it still loads comfortably.

For a personal website, that's a great performance.

Re: Twitter Is DDOSing Itself

#75

Post by Quarrelsome »

arter4 wrote: post #7

This 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 exponent…

I would guess the front end was written under the assumption that the back end would still work without auth. Perhaps the backend changes (mandatory auth + rate limiting) were pushed without sufficient testing of the front + back?

Re: Twitter Is DDOSing Itself

#76

Post by jrflowers »

kfrzcode wrote: post #57
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.

[flagged]

Seeing a random stranger on the internet and assuming they have three friends that use Mastodon isn’t really a big dunk on them or Mastodon

Re: Twitter Is DDOSing Itself

#77

Post by brucethemoose2 »

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.

Doesn't really matter if it works?

And if some massive org needs bandwidth for posts, can't they host their own public instance? I'm sure many organizations would prefer that over being at Twitter's mercy.

Re: Twitter Is DDOSing Itself

#78

Post by darkwraithcov »

Mizoguchi wrote: post #17

This kind of stuff is unavoidable with what's going on at Twitter. Infrastructure changes, platform changes and mass layoffs all at once. I'm actually impressed they haven't experienced more and longer outages.

Its a testament to how well designed and implemented the code base is, if the wheels havent started falling off yet (shockingly). I know we’re all supposed to shit on Twitter, but they had world class engineers working there before the mass layoffs and brain drain.

Re: Twitter Is DDOSing Itself

#79

Post by throwawat7832 »

mbrz wrote: post #70
throwawat7832 wrote: post #58

[flagged]

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

Re: Twitter Is DDOSing Itself

#80

Post by pronik »

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.
Post reply on HN