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

691–700 of 1001 posts

Re: Twitter Is DDOSing Itself

#691

Post by [deleted] »

nashashmi wrote: post #649
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.

The arrogance of the guy is so huge, hubris does not touch him. Thoughts are with the programmers. What I’m more surprised about is how gum and shoestring the twitter engineering is now a days. They put in no emphasis on doing deep divides into the code base and instead opt to do the simplest shortest fix. And it causes problems.

[deleted]

Re: Twitter Is DDOSing Itself

#692

Post by hvis »

martincmartin wrote: post #373
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…

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…

> My guess is Elon said "the site's too slow!"

Seems more like a thinly disguised attempt to force people to purchase subscriptions. Blue checkmarks and all.

Re: Twitter Is DDOSing Itself

#693

Post by kortilla »

cameronfraser wrote: post #680
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…

> So about the only thing they could do was issue multiple, parallel requests and hope that at least one of them was fast. lol nobody would do this to solve this problem because it doesn't even remotely solve it or give the appearance of solving it, if anything it's guaranteed to make things go slower

Google did this a long time ago. It’s more nuanced than you think. Two requests would be issued and the first acknowledged one cause the second to be cancelled. There was a public paper on this from Dean iirc and the method is a decade old.

Re: Twitter Is DDOSing Itself

#694

Post by SketchySeaBeast »

95014_refugee wrote: post #646
andsoitis wrote: post #507

Earlier quoted context omitted.

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

William of Ockham would like a word.

Ol' Billy Razor?

Re: Twitter Is DDOSing Itself

#695

Post by kevinventullo »

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…

Can you imagine Mark Zuckerberg writing these type of granular site outage status updates?

Re: Twitter Is DDOSing Itself

#696

Post by [deleted] »

voganmother42 wrote: post #667
TheHappyOddish wrote: post #664

Earlier quoted context omitted.

What holiday is it?

Is this really easier than consulting a calendar? Its the weekend before the 4th of July, the independence day for USA - many employers give employees Monday and Tuesday off, creating a potential four day break during what is typically very good weather - that being said Twitter is presumably (still) an international company with people in all different holiday areas.

[deleted]

Re: Twitter Is DDOSing Itself

#698

Post by chrisweekly »

WalterBright wrote: post #466
LiquidSky wrote: post #423

Earlier quoted context omitted.

From previous stories about Elon, telling him he’s wrong is a guarantee you’re going under that bus.

Every person in power is told he's wrong every day, all day, by most everyone. Heck, I've hired people to teach me things, told them they were wrong, and learned the hard way, many times.

> Every person in power is told he's wrong every day, all day, by most everyone.

Wait, what? That's a ridiculous assertion, even taken as hyperbole. A huge percentage of people in power surround themselves with "yes-men", and are allergic to (even constructive) criticism, let alone direct disagreement.

Re: Twitter Is DDOSing Itself

#699

Post by kevinventullo »

Solvency wrote: post #643
darkwraithcov wrote: post #78

Earlier quoted context omitted.

Its a testament to how well designed and implemented the code base is, if the wheels havent started falling off yet (shockingly). I know we’re all supposed to shit on Twitter, but they had world class engineers working there before the mass layoffs and brain drain.

I can easily visualize a wooden wagon rolling along a rocky slow descent forever and all of the reasons its wheels would eventually break loose. In the case of a platform like Twitter, aside from random acts of god and weather, aside from money, what are the sort of stuff that slowly breaks its wheels off over time such that, without staff, it inevitably stops working completely?

The ostensible cause for the rate limiting was “excessive scraping”. Battling stuff like this or e.g. spam bots is a constant arms race. So, without staff, the bad actors will eventually win.

Re: Twitter Is DDOSing Itself

#700

Post by sangnoir »

Xeamek wrote: post #369
roughly wrote: post #343

Earlier quoted context omitted.

That will be the case once H1-Bs are reformed and universal healthcare becomes real. Until then, this is an unrealistic and cruel position.

Nah, that's bs. Sure, if you are unskilled worker that's struggling from paycheck to paycheck, then you might not be able to easily change work. But in our line of work, and ESPECIALLY if you are good enough to work at something like twitter, pretending we are force to work where we are is a cope. Sure, maybe there are some extreme instances when it is the case, there are always exceptions. But on average, it's cring…

> But on average, it's cringe when people who earn literally twice what the average population does talk about "job insecurity" and pretend they are in the same boat as trully struggling lower class worker.

Because the Hedonic treadmill exists, expenses are also higher for high-earning people than the average population's: why would you expect well-paid folk not to worry about being unable to afford paying for their car note, mortgage, child-care and other obligations. Your position would be reasonable if all costs were uniform, and people who earn double put all their money in savings and investments.

Post reply on HN