3 ms·
> there were many contributing factors working together Looks like one factor, to my eyes: telemetry. I have telemetry disabled. But if you're going to defaul
by denton-scratch 5y ago
> there were many contributing factors working together
Looks like one factor, to my eyes: telemetry.
I have telemetry disabled. But if you're going to default to "telemetry on", and then silently send data to sites that aren't in the address-bar, then it's your responsibility not to "break the web". You can't blame it on rust, or necko, or viaduct, or google.
- Liquid_Fire 5y ago> This is why users who disabled Telemetry would see this problem resolved even though the problem is not related to Telemetry functionality itself and could have been triggered otherwise. It's pretty clear from the article that this was a bug, and telemetry requests failing was not intended to break the rest of the browser. If Google had rolled out this change a year from now, it could probably have broken something other than just telemetry (e.g. maybe update checks, or certificate management) and your browser would still have been broken even with telemetry disabled.
- hypertele-Xii 5y ago> It's pretty clear from the article that this was a bug, and telemetry requests failing was not intended to break the rest of the browser. If telemetry didn't exist as core part of the browser, nothing would've broken. Therefore, the telemetry itself is the direct cause of the bug. It was, at best, poorly handled and too deeply integrated into the browser's core function.
- matsemann 5y agoThe browser would have broken the next time a malformed http3 request happened. Read the quote again.
- pessimizer 5y ago> telemetry requests failing was not intended to break the rest of the browser. You can't find a lighter straw man than that. Find me somebody who said that Firefox intended to break the browser if telemetry failed.
- deleted 5y ago[deleted]