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

511–520 of 1001 posts

Re: Twitter Is DDOSing Itself

#511

Post by hn92726819 »

charcircuit wrote: post #186

It's not a self ddos if twitter isn't going down. You can see in the video twitter is properly handling the load and is returning HTTP 429 when the client is sending too many requests. Hitting the rate limiter or requesting a post is light weight. It's not like it's spamming login requests which require a lot of resources due to key stretching.

> It's not a self ddos

Maybe not

> if twitter isn't going down

I disagree. Ddos is a type of attack, not the result of an attack. If they're hitting their services way too many times in a distributed fashion, it's a ddos regardless of how it was handled.

Similarly, would you say this[0] wasn't a ddos because it was mitigated? I think not.

[0] https://blog.cloudflare.com/26m-rps-ddos/

Re: Twitter Is DDOSing Itself

#512

Post by [deleted] »

epistasis wrote: post #496
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.

I hate Elon's politics but want Twitter succeed. And if he didn't make his politics part of how he runs stuff, I probably wouldn't even care about his politics. But you know how celebrities get crap for inserting politics into things, when they know very little about that topic? Elon is going to get the same.

[deleted]

Re: Twitter Is DDOSing Itself

#513

Post by PestoDiRucola »

gitfan86 wrote: post #482
tmpz22 wrote: post #413

Can we please recognize that this is a holiday weekend and Elon rammed a big release forcing his engineers to come in and iterate multiple patches over the last 12 hours.

[flagged]

What kind of argument is this. So engineers have to pick between working on a long weekend and not shipping any code without any option in-between?

Re: Twitter Is DDOSing Itself

#514

Post by ikrenji »

cj wrote: post #392
baby wrote: post #362

Earlier quoted context omitted.

Employment is not the choice in the USA because health care is tied to it. The second reason is H1B.

> Employment is not the choice If you’re a software engineer anywhere in the US (with exception of H1B/TN/etc), where you work is 100% your choice. There isn’t a shortage of open engineering roles in this country. Nearly 100% of full time positions include fully paid healthcare.

bro i got 3.5 YOE and ive been applying in vain for the past couple of months. in my last job search i applied to ~ 10 positions and got 4 interviews...

Re: Twitter Is DDOSing Itself

#515

Post by tadfisher »

andsoitis wrote: post #507
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. Are you saying the engineers who are now at Twitter don’t have the right skills?

That's a non-sequitir. You can be at the top of your field and not completely understand a complex system. Also, the right people may not have even been involved in the implementation of this "feature".

Re: Twitter Is DDOSing Itself

#516

Post by goalieca »

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!

Re: Twitter Is DDOSing Itself

#517

Post by lolinder »

gitfan86 wrote: post #482
tmpz22 wrote: post #413

Can we please recognize that this is a holiday weekend and Elon rammed a big release forcing his engineers to come in and iterate multiple patches over the last 12 hours.

[flagged]

You seem to be positing that there are two choices:

1. Work for a toxic dictator who makes bad, micro-managed technical decisions and then expects his engineers to work a holiday weekend to clean up his mess.

2. Never ship code, ever.

I'm pleased to report that most software engineers exist happily somewhere in between these two extremes, and I would recommend you find a new job if you don't.

Re: Twitter Is DDOSing Itself

#518

Post by tadfisher »

beaned wrote: post #442
unconed wrote: post #422

Earlier quoted context omitted.

Except, progress grinding to a halt pretty much described Twitter before Elon Musk too. The story that anyone who knew anything was let go is just that, a story, as the number of employees by year shows Twitter, and other tech companies in the same period, overhired and then went back to pre-2020 levels. The only difference between then and now is that there is a big personality at the top who now personifies everyth…

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

That's... a perfectly reasonable position to hold?

Re: Twitter Is DDOSing Itself

#519

Post by ikrenji »

lmeyerov wrote: post #329

Apparently their 5-year cloud contract failed to renew today So, there may be a much simpler explanation for why their new rate limits on regular users to can-barely-scroll levels, and how that has all sorts of unintended consequences they weren't ready for

google wouldn't just shut off services for a big customer like that...
Post reply on HN