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

541–550 of 1001 posts

Re: Twitter Is DDOSing Itself

#541

Post by cyanydeez »

Topfi wrote: post #126

Speaking from very painful, personal experience, few things are more agitating than being forced to execute on something you fully know is a horrible idea, especially when you tried and failed to communicate this fact to the individual pushing you to go against your best judgement. Even more so when that person later loudly proclaims that they never made such a request, even when provided with written proof. I can of…

Ok, but the only people left are either hostages or sycophants.

Doubt either care at this point.

Re: Twitter Is DDOSing Itself

#542

Post by humean1 »

martincmartin wrote: post #373
Topfi wrote: post #126

Speaking from very painful, personal experience, few things are more agitating than being forced to execute on something you fully know is a horrible idea, especially when you tried and failed to communicate this fact to the individual pushing you to go against your best judgement. Even more so when that person later loudly proclaims that they never made such a request, even when provided with written proof. I can of…

The people at Twitter who understood the system and could predict the side effects were all fired or left. My guess is Elon said "the site's too slow!" Engineers noticed that the home feed request was slow. They didn't understand how it worked, had no tools to profile it, and were given an unrealistic deadline to fix it. So about the only thing they could do was issue multiple, parallel requests and hope that at leas…

> The people at Twitter who understood the system and could predict the side effects were all fired or left

And never created sufficient testing.

Re: Twitter Is DDOSing Itself

#543

Post by williamsmj »

walrus01 wrote: post #437
martincmartin wrote: post #373

Earlier quoted context omitted.

The people at Twitter who understood the system and could predict the side effects were all fired or left. My guess is Elon said "the site's too slow!" Engineers noticed that the home feed request was slow. They didn't understand how it worked, had no tools to profile it, and were given an unrealistic deadline to fix it. So about the only thing they could do was issue multiple, parallel requests and hope that at leas…

> The people at Twitter who understood the system and could predict the side effects were all fired or left. This is like a case study in what happens when you fire everyone except the sycophants and yes-men. I only feel sorry for remaining non-yes-men twitter employees who might still be there because for whatever personal reasons they're in a precarious economic situation where they can't quit (H1B?) or are tied to…

> This is like a case study in what happens when you fire everyone except the sycophants and yes-men.

The initial and biggest waves of layoffs last year were of people who hadn’t yet had a chance to demonstrate whether they were or were not sycophants. They were essentially random.

Re: Twitter Is DDOSing Itself

#544

Post by wongarsu »

jlund-molfese wrote: post #526
goalieca wrote: post #516

Earlier quoted context omitted.

I’ll play the devils advocate here but frontend devs need to smarten up. This is basic error handling that should have been in place for years. Blocking tweets with 403 or whatever they chose shouldn’t trigger endless retries on short intervals.. ever!

I’d bet (not that much, but like $20) that someone has a .ifClientError() or if responseStatus === 4xx somewhere. If you’ve never had to handle authorization in a particular area, it might have been safe to assume that any 4xx error should have been retried when the code was originally written and someone didn’t write them all out

But wouldn't responseStatus === 4xx indicate that the problem is on your end and retrying is unlikely to fix the issue. A 5xx is worth a retry, a 4xx should imho just produce an error message.

And even if you do retry, exponential backoff has been the standard for a long time (and is mentioned by the Twitter API documentation as a good solution to 429 responses)

Re: Twitter Is DDOSing Itself

#545

Post by 0xDEF »

I made an account around the time ChatGPT API (GPT-3.5) access was released to follow all the LLM news. The account is now getting aggressively rate limited that I cannot even see new tweets for 2-3 minutes.

Re: Twitter Is DDOSing Itself

#547

Post by DonHopkins »

1attice wrote: post #505
beaned wrote: post #442

Earlier quoted context omitted.

There's definitely a strong element of people here rooting for Twitter to fail because they dislike Elon's politics.

It is -- and I cannot stress this enough -- entirely OK to root for the failure of a company that is owned, directed and dominated by an odious person with abhorrent politics. Compare: - hoping Ballmer-era Microsoft would fail in their attempts to snuff out Linux - hoping that USSR would fail in their attempts to snuff out large numbers of their own citizens - hoping that the Confederates would fail at snuffing out r…

And speaking of having no gotcha but just being gotten, if you have showdead=true you can see one of Musk's biggest stans trevioustrouble rolling out their very best most deep and thoughtful arguments in support of Musk:

https://news.ycombinator.com/item?id=36556393

>trevioustrouble 1 hour ago [flagged] [dead] | parent | context | prev | next [–] | on: Twitter Is DDOSing Itself

>It’s just a feed, and needs to be rate-limited for unregistered users. No need to pull out your philosophy-degree. The people that were fired from Twitter were fired for good reason and if you think you’d do a better job than Elon with Twitter, you wouldnt.

>* PS: Dislike my comment fags

And then they sum up their politics and best arguments and what the Twitter they're fighting so hard for and what Musk they worship so much is all about, in just one word:

https://news.ycombinator.com/item?id=36556423

>trevioustrouble 1 hour ago [flagged] [dead] | parent | context | flag | vouch | favorite | on: Twitter Is DDOSing Itself

>fag

And that's the best they've got.

It really makes Musk's apologists so angry and frustrated to see everyone laughing their asses off at Musk explosively and bloodily sharting himself in public like that, because now they have to follow behind the elephant and wipe up all the mess.

Re: Twitter Is DDOSing Itself

#548

Post by hgsgm »

WalterBright wrote: post #486
Scalene2 wrote: post #463

Earlier quoted context omitted.

Except those who if they stopped working at Twitter could easily end up deported.

Having to leave the country and return home is not the same as slavery.

If you're going to be a vocal Libertarian you should be vocal about open borders for for jobs.

Re: Twitter Is DDOSing Itself

#549

Post by agentgumshoe »

cyanydeez wrote: post #541
Topfi wrote: post #126

Speaking from very painful, personal experience, few things are more agitating than being forced to execute on something you fully know is a horrible idea, especially when you tried and failed to communicate this fact to the individual pushing you to go against your best judgement. Even more so when that person later loudly proclaims that they never made such a request, even when provided with written proof. I can of…

Ok, but the only people left are either hostages or sycophants. Doubt either care at this point.

Or they're just people trying to earn their pay. Why must everything be a political divide these days...

Re: Twitter Is DDOSing Itself

#550

Post by sheepscreek »

goalieca wrote: post #516
Topfi wrote: post #126

Speaking from very painful, personal experience, few things are more agitating than being forced to execute on something you fully know is a horrible idea, especially when you tried and failed to communicate this fact to the individual pushing you to go against your best judgement. Even more so when that person later loudly proclaims that they never made such a request, even when provided with written proof. I can of…

I’ll play the devils advocate here but frontend devs need to smarten up. This is basic error handling that should have been in place for years. Blocking tweets with 403 or whatever they chose shouldn’t trigger endless retries on short intervals.. ever!

..and using exponential back-off, if not limiting the number of retries.

Though it’s hard to know for sure what really went down. Could be a number of things. Including a lack of subject matter experts (Elon recently admitted to laying off some people they shouldn’t have).

Post reply on HN