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

771–780 of 1001 posts

Re: Twitter Is DDOSing Itself

#771

Post by Sai_ »

phillipcarter wrote: post #446

All Elon had to do was leave it alone and, oh, right, the 44 billion. Hahahahaha! Man, Parag Agrawal and his team knew exactly what they were doing. A fool and his money are soon parted, indeed.

I have an alternative theory for this. Once Elon was forced by the DE court to buy Twitter, he went to autocrats and dictators with money and told them he'd burn Twitter to the ground on their behalf for 44B.

No Twitter, no Arab Spring. No live updates of disasters, no need to shutdown the internet to prevent dissenting voices from spreading.

Re: Twitter Is DDOSing Itself

#772

Post by eastbound »

mensetmanusman wrote: post #489
walrus01 wrote: post #437

Earlier quoted context omitted.

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

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

Meanwhile, France made mutuelle (half of the healthcare) mandatorily paid by employers. When you leave, you can keep it for a time, but it’s essentially paid by the employer…

Re: Twitter Is DDOSing Itself

#773

Post by NorwegianDude »

justcool393 wrote: post #506
kennywinker wrote: post #421

Earlier quoted context omitted.

I can't read that. "Something went wrong". And I believe under the new logged-in-only rules, I wouldn't even be able to read it if the site was up. Twitter links are now poisoned, and basically useless.

here are the tweets >To address extreme levels of data scraping & system manipulation, we’ve applied the following temporary limits: > >- Verified accounts are limited to reading 6000 posts/day >- Unverified accounts to 600 posts/day >- New unverified accounts to 300/day https://twitter.com/elonmusk/status/1675187969420828672 > Rate limits increasing soon to 8000 for verified, 800 for unverified & 400 for new unverif…

I have an idea. We should create a scaping system that scrapes all tweets and makes them availabe so that people are able to see what other people think they are linking to when they link to a broken Twitter page. /s

Either that or people should stop linking to broken pages.

Re: Twitter Is DDOSing Itself

#774

Post by danielheath »

concordDance wrote: post #327
epistasis wrote: post #286

Earlier quoted context omitted.

One thing about having leadership that is known to lie about anything or everything, for any sort of imagined personal gain, is that the very concept of truth is destroyed. I agree that this is probably not the bug at the root of it all. But I also don't believe the story that Musk is selling for why he's in effect shutting down the site. But both could be true and I'm still thinking about other potential reasons, a…

> One thing about having leadership that is known to lie about anything or everything, for any sort of imagined persona gain I will note that the few times I investigated claims of Elon lies they were not proper lies, either being misunderstood, misleading (which IS unethical, don't get me wrong), of indeterminate truth value (he said, she said type stuff), delusional optimism or actually true. Like journalists, Musk…

Which one of those did calling a cave-diving child rescuer a pedo fall under?

Re: Twitter Is DDOSing Itself

#775

Post by adamcblodgett »

Sai_ wrote: post #771
phillipcarter wrote: post #446

All Elon had to do was leave it alone and, oh, right, the 44 billion. Hahahahaha! Man, Parag Agrawal and his team knew exactly what they were doing. A fool and his money are soon parted, indeed.

I have an alternative theory for this. Once Elon was forced by the DE court to buy Twitter, he went to autocrats and dictators with money and told them he'd burn Twitter to the ground on their behalf for 44B. No Twitter, no Arab Spring. No live updates of disasters, no need to shutdown the internet to prevent dissenting voices from spreading.

Are we doing theories? Mine is that Peter Thiel sold Musk on buying Twitter by convincing him of his ability to make it profitable with his genius, knowing full well he'd sink the thing in 18 months, and another pesky tool would be off the table for awhile.

Re: Twitter Is DDOSing Itself

#776

Post by sh34r »

AbraKdabra wrote: post #660
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 feel very sorry for the people forced to work at that company under that management. Forced? You know slavery was abolished a long time ago no?

Unless you are in prison. You think I'm BSing then read the 13th amendment.

Re: Twitter Is DDOSing Itself

#777

Post by j16sdiz »

Rimbo wrote: post #676
sigzero wrote: post #622

Earlier quoted context omitted.

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

You might be right; the person you're replying to might have zero idea. Now me... I know someone personally who was a senior exec for Twitter's software team, who left after Elon's purge. He left because all the people who understood the system and could predict the side effects were fired or left. He'd been with companies going through death spirals before, and had no interest in being involved with another one. So,…

I don't know you or your friend, but thinking how dreadful some hiring process can be, I would defer changing my job as much as possible..

Re: Twitter Is DDOSing Itself

#778

Post by rkagerer »

ineedasername wrote: post #749
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 Not necessarily. I’ve predicted bad outcomes for decisions in a few cases and been ignored but stuck around regardless. Mostly because I like my job and the goals of my organization even if it makes bad decisions. Of course to remain productive and improve my influence in future decision making it is absolutely…

Thanks for your good work.

Re: Twitter Is DDOSing Itself

#779

Post by abenga »

andsoitis wrote: post #611
fundad wrote: post #375

Earlier quoted context omitted.

[flagged]

> Not Twitter, the racist bullshit artist who bought it. Can you explain why a racist would give internet access (Starlink) to 50 schools in Rwanda? https://twitter.com/Starlink/status/1671930585475055618

Is this the philanthropic "I can't be racist! I have Black friends!" reply?

Re: Twitter Is DDOSing Itself

#780

Post by ezoe »

samb1729 wrote: post #301
comboy wrote: post #59

Anybody knows if these requests were happening before the login only change? Because it would be hilarious if huge scrapping operation was a bug in their javascript.

I've noticed the frontend hammering the backend quite often in the past few weeks. It would not surprise me at all to learn that the "influx of scraping" was mostly Twitter's fault.

Are you suggesting Elon found out the true culprit the hard way?
Post reply on HN