Live data from Hacker News

Twitter Is DDOSing Itself

sfba.social

501–510 of 1001 posts

Re: Twitter Is DDOSing Itself

#502

Earlier quoted context omitted.

Between visa and healthcare matters there are undeniably employees in that exact predicament.

[flagged]

Healthcare expenses are a huge fraction of a person's "income" but it's not usually counted part of their top line compensation number.

So paying COBRA might be 20% of your prior income, at the same time as losing all your income and still having to pay your rent and all other expenses.

Re: Twitter Is DDOSing Itself

#504
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]

Some of the remaining engineers may be stuck due to H1B

Re: Twitter Is DDOSing Itself

#505
post #442

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.

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 resistance to literal slavery

- (in fiction,) hoping that the Death Star would fail at snuffing out various planets, etc

and so forth.

There is not some weird list of permissible root-reasons. You have no gotcha; you are just gotten.

Re: Twitter Is DDOSing Itself

#506
post #382

Matters little, but the rate limits are opening back up. 6k/600/300 -> 8k/800/400 (~noon) -> 10k/1k/500 (~3pm) https://twitter.com/elonmusk/status/1675214274627530754 and self-reply

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 unverified

https://twitter.com/elonmusk/status/1675214274627530754

> Now to 10k, 1k & 0.5k

https://twitter.com/elonmusk/status/1675260424109928449

Re: Twitter Is DDOSing Itself

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

Are you saying the engineers who are now at Twitter don’t have the right skills?

Re: Twitter Is DDOSing Itself

#508

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…

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…

What a fantastically bad take supported by no facts whatsoever. I like your graphics work but you should really think before you type this kind of a thing up.

Re: Twitter Is DDOSing Itself

#510

Earlier quoted context omitted.

>has made way for free-speech Here’s just a few of the people (in these cases journalists) that Elon has banned. It’s not hard to find other examples of censorship either. That’s his right, he owns all of it, but he lied about ideals of free speech. If it’s speech he doesn’t like, he kills it: Ryan Mac Drew Harwell Micah Lee Matt Binder Aaron Rupar Donie O’Sullivan Tony Webster EDIT: these bans were related to report…

For posterity, those journalists were banned (unbanned a few months later) for just reporting on ElonJet, who used publicly available FAA data to track Elon's jet. Elon called it doxxing. And also temporarily banned links to Mastodon just to prevent people from accessing ElonJet that way. https://en.wikipedia.org/wiki/ElonJet

Good point, they were all related as bans resulting from reporting or tweeting about the elonjet ban. I edited my comment accordingly since it’s important context to know the ones I mentioned were all related to a single event (though he’s silenced others as well for different reasons too)
Post reply on HN