Twitter Is DDOSing Itself • Hacker News Board

Re: Twitter Is DDOSing Itself

#381

Post by tro2102 » Sat, Jul 01, 2023, 11:15 PM UTC

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…

Did you ignore "H1-B" on purpose?

Re: Twitter Is DDOSing Itself

#382

Post by mcint » Sat, Jul 01, 2023, 11:15 PM UTC

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

Re: Twitter Is DDOSing Itself

#383

Post by partiallypro » Sat, Jul 01, 2023, 11:15 PM UTC

summerlight wrote: post #364

> If you missed the initial news of the impending showdown, Platformer reported on June 10th that Twitter had been refusing to pay Google for its cloud services ahead of their contract’s June 30th renewal date. > Twitter’s Google Cloud contract dates back to 2018. https://www.engadget.com/twitter-has-supposedly-started-payi... Oh... this explains all this fiasco :facepalm:

As the article says, and as Bloomberg, etc have also reported. Twitter finally agreed to play nice with Google and the issue was resolved. They are probably trying to get off of GCP, but this isn't because they suddenly lost access to GCP from payment refusal.

Re: Twitter Is DDOSing Itself

#384

Post by steveBK123 » Sat, Jul 01, 2023, 11:16 PM UTC

jaggederest wrote: post #358

Waterluvian wrote: post #275

Earlier quoted context omitted.

If executives are throwing you under a bus, make an exit. There’s no coming back from a clown show like that.

I have a general rule that I make proactive, diligent efforts to inform and correct, and I do it 3 times to 3 different groups in leadership, and if that doesn't work, I'm out. I'm about 2 for 8 but you gotta try sometimes.

Yeah more often than not people just really really want to touch the hot stove.

Being the bearer of bad “stoves are hot to the touch” news makes you a downer.

Re: Twitter Is DDOSing Itself

#385

Post by [deleted] » Sat, Jul 01, 2023, 11:16 PM UTC

macintux wrote: post #313

skymast wrote: post #306

Earlier quoted context omitted.

[flagged]

Are you by any chance working 40 hour weeks?

[deleted]

Re: Twitter Is DDOSing Itself

#386

Post by turtleyacht » Sat, Jul 01, 2023, 11:16 PM UTC

avereveard wrote: post #34

I've a scalability problem I'll add a dedicated microservice I've now two scalability problems

As a haiku:

  I can't scale this more
  I'll add a microservice
  I can't scale these more

Re: Twitter Is DDOSing Itself

#387

Post by partiallypro » Sat, Jul 01, 2023, 11:17 PM UTC

kristianc wrote: post #319

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…

That’s exactly it. Musk a week ago was telling us that there were a record number of user seconds on the site. Now he’s telling us they’re all content-scrapers. The very concept of truth is eroded.

That's what makes it so perfect when he echos conspiracy theories, Russian talking points, and other whacky talking points and elevates untrustworthy sources by tweeting things like "interesting" catapulting them into everyone's feed.

Re: Twitter Is DDOSing Itself

#388

Post by goodbyesf » Sat, Jul 01, 2023, 11:17 PM UTC

epistasis wrote: post #286

aeyes wrote: post #272

This bug is very unlikely to be the reason. The rate limiter on the server side is cheap and the frontend bug only gets triggered with the rate limit active. I have seen similar bugs in the systems I oversee because network libraries love to retry requests without sane limitations by default. But I never saw them make our rate limiters sweat. It's slightly more annoying when they hit an API which actually does some e…

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…

[flagged]

Re: Twitter Is DDOSing Itself

#389

Post by TheBlight » Sat, Jul 01, 2023, 11:17 PM UTC

I don't see any unusual behavior when looking at the debugger in Chrome. People have a political issue with Elon. Which is fine. People are entitled to it.

Re: Twitter Is DDOSing Itself

#390

Post by eyelidlessness » Sat, Jul 01, 2023, 11:18 PM UTC

drekipus wrote: post #318

beebmam wrote: post #299

Earlier quoted context omitted.

A union vote is the only way to save that platform. Either unionize or let the company die.

Unions are for the people, not the company

Unions are generally predicated on representing their members, but there are countless permutations of nuance where such representation would also benefit or protect the company, at least to some extent.