Reporting it publicly this way can also be a favor to both, as it gives them a fairly malleable narrative for reversing course, or directing responsibility, or both. Even if it’s simultaneously embarrassing to have it out there. And it’s not like either Musk or Twitter is a stranger to embarrassment, or particularly shy about courting it.
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.
Maybe that theory is correct. But I feel like pretending this post is getting to the top of HN because it's a technically interesting diagnostic analysis is sort of silly.
It can take a lot of time and effort to develop instincts like “scrollbar jumping and network calls are related”. They’re so obvious to me that I didn’t even bother inspecting anything, I just “debugged” on my phone by connecting familiar dots and describing the familiarity. But if it’s not immediately obvious to you and if you have an inclination to be more familiar, I’d strongly recommend spending more time manually fuzzing rando sites with dev tools open. You’ll probably get a lot more out of that than dissecting personal motivations on any thread on any site. And you’ll have a much better calibrated bullshit detector too.
it's a 429 error, so the developer who posted this is an idiot. they're not even wrong. the 429 doesn't even touch twitter's infrastructure
https://blog.twitter.com/engineering/en_us/topics/infrastruc...