Live data from Hacker News

Twitter Is DDOSing Itself

sfba.social

751–760 of 1001 posts

Re: Twitter Is DDOSing Itself

#751

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. You have zero idea if that is true or not.

The current state of Twitter seems to indicate there's a significant problem with the code, which implies the people who would have either spotted that before it was deployed or fixed it quickly afterwards, are unable to do so. Given the number of layoffs and resignations Occam's Razor would suggest the reason is because those people aren't available to do that work.

We don't kmow it's true but it is a likely explanation.

Re: Twitter Is DDOSing Itself

#752
post #629

Earlier quoted context omitted.

Yeah I wish Obama care had simply been: 'employer provided healthcare is illegal in 2024'

That wasn't possible, having Lieberman's vote was required, and he said no to anything like that

Plus, health care spending is like >10% of GDP. You don't rewrite the rules like that with upsetting a great deal of corporate interests. An appreciable number of people benefit from all the inefficiency in delivering health care.

Re: Twitter Is DDOSing Itself

#753

Don't interrupt your opponent when they are making a mistake.

Why do people oppose Twitter? It's a social network, you can choose not to use it.

That social network shut prominet scientists voice during the COVID that's why many people like me hate it

Re: Twitter Is DDOSing Itself

#755
post #731

Earlier quoted context omitted.

He did make the call to do that, did he not? He publicly stated it on Twitter.

Why does it matter that he made the call to do that? I get plenty of "do this, do that" requests from my manager. And if I break things, is it my manager's fault? I'm trying to understand your logic. Please, explain. Edit: here is my take on it + the most likely scenario of what's going to happen next. This was a bad deployment and such things are not unusual in software industry. In this specific case, there are zer…

If you inform your manager that doing X could break the site and they still push for it, then it is in fact their fault when it breaks.

The point of a decision-maker is to make informed decisions, if you fail to do that, then you fail at leadership.

Re: Twitter Is DDOSing Itself

#756

Earlier quoted context omitted.

> The people at Twitter who understood the system and could predict the side effects were all fired or left And never created sufficient testing.

You can't write tests for the changes someone might make in the future.

That's exactly why you write tests. You want to be sure future changes don't break present functionality, especially if the future changes are being done by someone who doesn't understand your part of the system.

Re: Twitter Is DDOSing Itself

#757

It's an interesting theory but the DDoS predates the decision to disable anonymous access. In fact, that decision was taken in order to mitigate an ongoing DDoS[0][1]. So while it's possible that the questionnable web front end retry logic is not helping things, it's not the root cause. [0] https://twitter.com/elonmusk/status/1674865731136020505 > Temporary emergency measure. We were getting data pillaged so much tha…

Honestly it probably has more to do with the decision to basically shut down API access without exorbitant fees than it has to do with AI startups or whatever.

Surely there are some colossal archives of all tweets before whatever date floating around that those startups are using instead.

Re: Twitter Is DDOSing Itself

#760
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'm going through this right now in my job, having built a tool to manage vulnerability tickets for my team, and having it's first use be deleting every vulnerability ticket, despite my protests. The person executing this is more concerned about looking good on paper than actually improving security.
Post reply on HN