Hacker News new | ask | show | jobs
by the42thdoctor 1086 days ago
I think he was trying to say that the Frontend of the Twitter timeline is not aware of the new request limit, and when that limit is reached it just retries the request, as it would in a normal network error, and keeps in retrying resulting on DDOS.

But I don't believe on that because Twitter is a billion dollar company and that kind of mistake is dumb. So idk.

5 comments

> But I don't believe on that because Twitter is a billion dollar company and that kind of mistake is dumb.

This sort of mistake is very common especially when a product is going through a period of change, so it seems very believable to me that recent rate limiting features (or older features that have not been used in a long time or maybe ever) on the backend hadn't been adequately tested to make sure there are no unforeseen side-effects on the front-end when they are activated under pressure.

Very common for start ups with inexperienced devs, not for long standing tech companies with the best and most experienced employees...

Isn't Elon supposed to know this shit himself?

I guess we learned alot about the state of the company as well as elons own coding skills with this event, didn't we?

Even in “long standing tech companies with the best and most experienced employees” this sort of issue has been known to fall through the cracks. Twitter has experienced significant staffing changes, procedure changes, and code changes, recently and any one of those three things can exacerbate the chances of side-effects of changes not being realised until too late.
When you buy a company and your staff has had near complete turnover and your product significantly changes (at least in consumers eyes), are you actually the same company?

I'd say that shortly after Elon bought it twitter effectively became a start-up rather than an established company.

Arguing otherwise is like saying Xerox Park would have been the exact same institution even if all the staff were swapped with interns and management fundamentally change mission statements etc.....

Kind of absurd when framed that way, huh?

You severely overestimate musk’s software engineering prowess
The people who had the knowledge to realize this was a dumb mistake were probably fired by Musk.
Then you didn't look at how any of the Atlassian products are built. Most of them are multiple implementations of the same Frontend-Franework on the same page because independent teams work on stuff. Then you have hundreds of request "just to load some issue list".

Probably twitter can even do worse.

I wouldn't have believed it but we're seeing it happen in real time haha. How twitter has fallen from the glory days