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

411–420 of 1001 posts

Re: Twitter Is DDOSing Itself

#411

Post by SSLy »

screye wrote: post #140
hinkley wrote: post #120

Earlier quoted context omitted.

When someone says, "certain topics will get you banned" that doesn't make me judge the platform, that makes me judge the person. People are going to assume it's something you don't want to name, if you won't name it.

Come on, in a lot coastal discourse it is practically taboo to mention vanilla opinions that are held by 70+% of the population. Mastodon instances are largely moderated by people from the other 30%. You are free to judge if you want. But don't pretend this is a violation of publicly accepted morals in the 1st world.

Coastal? Like, related to beaches, tides, or some kind of environmental impact?

Re: Twitter Is DDOSing Itself

#413

Post by tmpz22 »

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.

Re: Twitter Is DDOSing Itself

#414

Post by eyelidlessness »

TheBlight wrote: post #409
eyelidlessness wrote: post #406

Earlier quoted context omitted.

The post suggests a race condition as the underlying cause of the behavior shown in screen captures. It’s perfectly possible the race condition does exist, and being a race condition you just didn’t happen to trigger it. It’s also perfectly possible to discover such a defect with or without any personal bias towards Musk or Twitter. Reporting it publicly this way can also be a favor to both, as it gives them a fairly…

Clearly there is something wrong with the site. So I don't doubt there is a bug. But the OP gives no helpful information that could be used to reproduce the issue and fails to describe it in any helpful detail really. They seem content to just effectively say "Twitter is dumb." Which, again, is fine but not all that technical and interesting.

There’s information in the post that very probably points at the underlying cause. The scrollbar jumping is a dead giveaway: Twitter loads more content based on scroll position. If your viewport is sized such that displaying the error message triggers another load event by its corresponding change in scroll position, it will try again indefinitely absent some additional logic to bail out.

Edit: this of course depends on some other implementation details, like the rendering flow and browser behavior. If showing the error is memoized, it shouldn’t trigger the loop unless they’re also rendering some intermediate loading state asynchronously.

Re: Twitter Is DDOSing Itself

#415

Post by IAmGraydon »

craig1f wrote: post #15

[flagged]

There are many thousands of forums, but do remember that there was a time (not that long ago) that social networks didn’t exist and things seemed a hell of a lot more rational back then. Both Reddit and Twitter have been highly weaponized by both foreign and domestic entities. If this is a concerted effort to destroy social media (and I’m not so convinced it is), I think it’s not a bad thing. It’s just become extremely toxic and even dangerous for society.

Re: Twitter Is DDOSing Itself

#416

Post by jitl »

noarchy wrote: post #271
jitl wrote: post #8

Bluesky feels like it’s buckling under the refugee crisis load

I've been on their waiting list for what seems like months at this point. Huge missed opportunity for them, being unable to leverage Twitter's failings.

Based on app perf today, they’re probably metering signups for good reasons.

Re: Twitter Is DDOSing Itself

#417

Post by henry2023 »

8organicbits wrote: post #377
oblio wrote: post #339

Earlier quoted context omitted.

What do you mean?

Jitter is a little randomness in how long clients wait between retries. It ensures that you don't have a "thundering herd" all retrying at the same time. Imagine if your API used exponential backoff of [1s, 2s, 4s, 8s, ...] and a large group of requests gets a retryable error at t=0. They will all retry at exactly t=1, t=2, etc. If the group is large enough that repeated surge of requests can knock you offline. There…

I enjoyed your comment a lot. Interesting to think that abstract structures like a load balanced webserver have a simil to the fundamental frequency observer in physical structure

Re: Twitter Is DDOSing Itself

#419

Post by vuln »

readyplayernull wrote: post #184
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…

Could someone report the error at press@twitter.com and see what they think about it?

Quite the knee slapper. Thanks. I hope you didn’t spend many brain cycles on it.

Re: Twitter Is DDOSing Itself

#420

Post by EdwardDiego »

Sparyjerry wrote: post #285
Mizoguchi wrote: post #17

This kind of stuff is unavoidable with what's going on at Twitter. Infrastructure changes, platform changes and mass layoffs all at once. I'm actually impressed they haven't experienced more and longer outages.

True, the rate of improvements has been insane. I use it pretty often and haven't even noticed a second of unavailability even today and right now, not to say I use it 24/7 though. It's pretty obvious some people have a political bend to their hatred of Twitter so any second something isn't perfect they jump on it. It's really a sad state of affairs really.

Political bent?

Can't I just think Elon Musk is a twat without it being somehow political?

Post reply on HN