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

931–940 of 1001 posts

Re: Twitter Is DDOSing Itself

#931

Post by paxys »

joe__f wrote: post #762
paxys wrote: post #572

Earlier quoted context omitted.

Twitter Engineers have had over a year to get out and find another job. At this point the terms of their employment and the expectations from their boss are all crystal clear. Hard to sympathize with those who continue to stick around for whatever reason.

You are telling people who are being abused that it's their fault that they didn't leave. This is victim blaming.

The actual insulting part is telling a group of skilled individuals who are willingly working a job and getting a good salary that they are "victims" and helpless and abused. Maybe let them do their thing, and you do yours. There's no need to be outraged on behalf of anyone else.

Re: Twitter Is DDOSing Itself

#932

Post by dyno12345 »

berkle4455 wrote: post #654
pschuegr wrote: post #598

Earlier quoted context omitted.

This. I'd bet substantial amounts of money that the evil scraper idea is the result of a) another issue + b) paranoia + c) Musk thinking he understands better than anybody else.

This is a really ignorant take to dismiss scrapers. LLMs operate by having petabytes of conversational training data. Scraping is how OpenAI trained GPT. It’s how all their copycats are trying to do the same. Elon can be a monumental asshat, and he can be self-DDOS’ing, and can be accurate about scraping at the same time. It’s why every single social media platform is heading toward becoming a walled garden.

How do you feel about search engine indexing?

Re: Twitter Is DDOSing Itself

#933

Post by dopa42365 »

Brybry wrote: post #138
teawrecks wrote: post #72

Earlier quoted context omitted.

Also most of the rest of the world doesn't use Twitter (I'm seeing about 240M total users?). The ones that do use Twitter do so because of a significant amount of money going into marketing Twitter's platform. Conversely, relatively nothing goes into pushing people to use mastodon. It can only take off if it really does prove, not just useful, but more useful than a centralized version that's got money behind it.

What microblogging service does most of the rest of the world use? Weibo? Telegram channels?

Twitter is basically a platform for social media managers, no one uses it to stay in touch with their 20 friends. Memefied prnewswire.

This "famous person/brand posts something medium witty 10 times a day, urge to consume intensifies" thing isn't that popular worldwide.

Re: Twitter Is DDOSing Itself

#934

Post by delecti »

rideontime wrote: post #467
mcint wrote: 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 managed to hit the (newly raised?) rate limit simply by tapping that link. What a circus.

Yeah, between the rate limit, and the algorithmic weighting toward "blue" users, there's very little incentive to interacting with high-follower accounts at the moment.

Re: Twitter Is DDOSing Itself

#935

Post by colechristensen »

kccqzy wrote: post #499
arter4 wrote: post #7

This is interesting. Judging from the screenshot, a huge amount of GET /TweetDetail is generated which triggers some rate limiting, as shown by the 429. If this is indeed due to the recent decision to enforce authentication for all API calls, it means the curlprit may actually be the API gateway or something similar downstream. Also, this behavior seem to never stop, which isn't what one would expect from an exponent…

While exponential backoff is theoretically optimal, I doubt it's actually used that often in practice. I've seen too many cases where someone decides serving user requests with low latency is so important that they'd rather have a constant randomized backoff than exponential backoff. I've been in many design meetings and seen enough documents where the decision not to use exponential backoff is explicitly made, under…

I’ve had to… uhh… eagerly advocate for exponential backoff for weeks of constant uptime issues before someone listened and actually implemented it and solved the problems.

Like several times in different roles.

People do it, exponential backoff is everywhere in your stack, but it doesn’t end up in your application layer until you have enough traffic that you actually have to manage throughout.

Re: Twitter Is DDOSing Itself

#936

Post by colechristensen »

cactusplant7374 wrote: post #84
arter4 wrote: post #7

This is interesting. Judging from the screenshot, a huge amount of GET /TweetDetail is generated which triggers some rate limiting, as shown by the 429. If this is indeed due to the recent decision to enforce authentication for all API calls, it means the curlprit may actually be the API gateway or something similar downstream. Also, this behavior seem to never stop, which isn't what one would expect from an exponent…

Did Elon pay the AWS bill? That seems like a likely culprit. Twitter instances are being forcibly shutdown.

This is not remotely a likely culprit.

Re: Twitter Is DDOSing Itself

#938

Post by yxre »

goalieca wrote: post #516
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’ll play the devils advocate here but frontend devs need to smarten up. This is basic error handling that should have been in place for years. Blocking tweets with 403 or whatever they chose shouldn’t trigger endless retries on short intervals.. ever!

I don't think its intentional. I think it's a side effect of using a listener pattern.

If you use a listener, useEffect in react, to load data, it will start the request, track it is loading with a boolean, and then store the payload. That passes unit tests and QA.

If the listener doesn't check the error before starting the api request again, you have this infinite loop happen where the loading flag goes off and the payload is still null, so it just starts it again.

It's sloppy code, but its an unintentional side effect.

Re: Twitter Is DDOSing Itself

#939

Post by jquery »

quenix wrote: post #809
sh34r wrote: post #763

I'm astounded it took this long to finally die. All those Twitter engineers who were harassed by Elmo's very online fan club, and were treated with such cruelty and disdain on their way out, clearly did an incredible job. Hats off to them. The curse of IT Operations: if you do everything right, management grifters never think you did anything at all. Why do I need you? Everything works fine! Most Internet platforms a…

> He has no STEM degree. Musk has a bachelor's degree in physics from the University of Pennsylvania: https://www.snopes.com/fact-check/musk-physics-degree/ . Further, while I share some criticism of the man, many very technical people from companies such as SpaceX and Tesla have come forward with public comments, praising him for "truly grasping the engineering" and "being involved in every technical design decision…

Instead of judging Elon by quotes from people who might have something to gain by praising a narcissist, how about we judge Elon by the insanely dumb things he says and does on a near daily basis?

And you're right he has a degree, although he repeatedly lied about when he received it, and even lied about where he received it, so please forgive people for their confusion.

Re: Twitter Is DDOSing Itself

#940

Post by ricardobeat »

yxre wrote: post #938
goalieca wrote: post #516

Earlier quoted context omitted.

I’ll play the devils advocate here but frontend devs need to smarten up. This is basic error handling that should have been in place for years. Blocking tweets with 403 or whatever they chose shouldn’t trigger endless retries on short intervals.. ever!

I don't think its intentional. I think it's a side effect of using a listener pattern. If you use a listener, useEffect in react, to load data, it will start the request, track it is loading with a boolean, and then store the payload. That passes unit tests and QA. If the listener doesn't check the error before starting the api request again, you have this infinite loop happen where the loading flag goes off and the…

Minor correction, this is not a listener pattern, but React’s hook-based reactivity DSL.

It’s actually exactly the type of problem declarative UI libraries like react were supposed to prevent, yet here we are 8 years later.

Post reply on HN