Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> That's not what happened though

What do you mean that's not what happened? Was there a "Firefox outage" or not? Are you disputing claims that the engineering team made about Firefox becoming unusable for users "for close to two hours"?



> about this telemetry bug

That's my point. A "telemetry bug" didn't make Firefox unusable, a networking bug that was triggered by a telemetry bug did. But it could just as easily have been triggered by anything else.


First, you're going anachronistic. They didn't write "telemetry bug".

Secondly, "cause" doesn't automatically mean "root cause". (That's the entire reason we distinguish between the two by qualifying the latter to begin with.) It's perfectly reasonable to say "A caused B" even if the root cause lies elsewhere, with C.

Thirdly, none of this matters. It has no impact on the point being made by the person you responded to, which—to repeat—is that:

> It should be impossible for the phrase "the recent Firefox outage" to make sense.


>It should be impossible for the phrase "the recent Firefox outage" to make sense.

It makes perfect sense a world where half the internet is going through Google / Cloudflare / Amazon /Akamai servers or some combination of the above, and they decide to roll out brand-spanking-new protocols to half of the internet at once. Sometimes that's going to break clients.

I don't like that world very much, but it's the one we live in.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: