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

221–230 of 1001 posts

Re: Twitter Is DDOSing Itself

#221

Post by firesteelrain »

lr4444lr wrote: post #207
lamontcg wrote: post #143

I think we're about at the point where the people who predicted chaos at twitter after Elon basically fired most of the experienced engineers have been proven correct. The duct tape is all coming apart at the seams now. It isn't quite as decisive as a submarine imploding, and ceasing to exist, but it has turned into a brightly burning tirefire.

I dunno. We are several months out after the major layoffs. Maybe some very recent bad decisions were made internally that pared back too far, but I think Musk has long since been proven correct that the core platform could function on a fraction of the workforce it had at the time of takeover.

Agree. Plus it’s easy to crap on Elon but it’s also the poor Twitter architecture and quality of people they have working for them that caused this despite Elon’s desire to require login to read Twitter. He didn’t write the code.

Re: Twitter Is DDOSing Itself

#222

Post by simonw »

lr4444lr wrote: post #207
lamontcg wrote: post #143

I think we're about at the point where the people who predicted chaos at twitter after Elon basically fired most of the experienced engineers have been proven correct. The duct tape is all coming apart at the seams now. It isn't quite as decisive as a submarine imploding, and ceasing to exist, but it has turned into a brightly burning tirefire.

I dunno. We are several months out after the major layoffs. Maybe some very recent bad decisions were made internally that pared back too far, but I think Musk has long since been proven correct that the core platform could function on a fraction of the workforce it had at the time of takeover.

Complex systems like Twitter don't break overnight when you lay off the talented engineers.

They deteriorate piece-by-piece, potentially over the course of many months, until the compounding effects of these problems and the growing technical debt overwhelms the team that they have left.

Re: Twitter Is DDOSing Itself

#223

Post by [deleted] »

screye wrote: post #140
hinkley wrote: post #120

Earlier quoted context omitted.

When someone says, "certain topics will get you banned" that doesn't make me judge the platform, that makes me judge the person. People are going to assume it's something you don't want to name, if you won't name it.

Come on, in a lot coastal discourse it is practically taboo to mention vanilla opinions that are held by 70+% of the population. Mastodon instances are largely moderated by people from the other 30%. You are free to judge if you want. But don't pretend this is a violation of publicly accepted morals in the 1st world.

[deleted]

Re: Twitter Is DDOSing Itself

#224

Post by simonw »

firesteelrain wrote: post #221
lr4444lr wrote: post #207

Earlier quoted context omitted.

I dunno. We are several months out after the major layoffs. Maybe some very recent bad decisions were made internally that pared back too far, but I think Musk has long since been proven correct that the core platform could function on a fraction of the workforce it had at the time of takeover.

Agree. Plus it’s easy to crap on Elon but it’s also the poor Twitter architecture and quality of people they have working for them that caused this despite Elon’s desire to require login to read Twitter. He didn’t write the code.

Elon is responsible for the quality of the people who work for Twitter. That's what a CEO does.

Re: Twitter Is DDOSing Itself

#225

Post by avl999 »

lamontcg wrote: post #143

I think we're about at the point where the people who predicted chaos at twitter after Elon basically fired most of the experienced engineers have been proven correct. The duct tape is all coming apart at the seams now. It isn't quite as decisive as a submarine imploding, and ceasing to exist, but it has turned into a brightly burning tirefire.

I am not disagreeing with you but self-ddos is not entirely uncommon. When I worked at Amazon this would happen a few times a year. Not on the main amazon.com website but on supporting services often initiated by but not limited to kindle devices. Having something like this slip through the cracks of even experienced engineers isn't uncommon.

Re: Twitter Is DDOSing Itself

#226

Post by rvba »

epistasis wrote: post #167
brucethemoose2 wrote: post #33

Also, taking Elon's word at face value for a second... is Twitter really worth scraping for AI training or whatever? Its a hive of misinformation, disinformation and toxicity. Its succinct I guess, but nothing is eloquent or descriptive because of the character limit. And its full of repetitive "filler" information. Who wants that in a foundational LLM dataset? Maybe its OK for finding labeled images... But that stil…

While there may be huge sections of Twitter content that are like what you describe, I haven't encountered that. Instead I see tons of hyper-focused discussion from very specialized scientists that I wouldn't see otherwise. I see lots of discussion if obscure housing policy, that I wouldn't see otherwise. Now, this has been severely degraded by the changes that Musk has made. The spam in direct messages is off the ch…

As someone who doesnt use twitter, I dont understand how can you have any sort of a real discussion with a 140 character limit.

The best discussion platform is IMHO the older version of reddit / i.reddit with the nested comments + possibility to be indexed by google + possibility to reply to old posts. The super-nesting comments feature is great.

Re: Twitter Is DDOSing Itself

#227

Post by hyperpape »

bravoetch wrote: post #176
lamontcg wrote: post #143

I think we're about at the point where the people who predicted chaos at twitter after Elon basically fired most of the experienced engineers have been proven correct. The duct tape is all coming apart at the seams now. It isn't quite as decisive as a submarine imploding, and ceasing to exist, but it has turned into a brightly burning tirefire.

25 years of products being honed for shareholder value, instead of customer or user value. We may be at peak consumer tolerance for anti-pattern, in-app purchase, subscription-model, ad-packed, data-siphoning, dopamine driven, gated experiences.

This is a perfect example of how "shareholder value" is a thought-terminating cliche.

Twitter was previously a public company, which was beholden to shareholders, and aimed to try and increase its stock price (as far as "shareholder value" actually means anything, this is basically it). I wouldn't praise previous management (the company wasn't profitable), but they were not a complete dumpster fire.

Then Twitter was bought out, and taken private, removing the obligation to "shareholder value." The ensuing dumpster fire is one that will be marveled at for years.

I'm not saying public corporations are better than private, or that "shareholder value" is a good slogan. I'm just saying that your comment is every bit as irrelevant as the porn spam that's clogging Twitter these days. (Thanks for fixing the spam problem, y'all!).

Re: Twitter Is DDOSing Itself

#228

Post by distantsounds »

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.

previous HN articles linking to instances has caused them to become overloaded. this instance just seems to know how to handle it

Re: Twitter Is DDOSing Itself

#229

Post by viraptor »

agluszak wrote: post #132
pronik wrote: post #80

Earlier quoted context omitted.

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

Mastodon doesn't have the incentive to go to shit, as there's no company trying to earn as much money as possible behind it.

Apart from Facebook (I mean Meta (I mean Threads)). Let's see how that one plays out, but initially it seems like they'll be blocked by almost every bigger instance anyway.
Post reply on HN