Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
> So you're saying telemetry should be handled as a separate process that has nothing to do with the rest of the browser, and treated like a hostile service? [... T]his was a dumb bug and it is completely unreasonable to expect some kind of adversarial design "just in case a freak bug triggers on telemetry network requests".
I absolutely agree that this a dumb bug having little to nothing to do with telemetry. It is not even the first case-sensitivity HTTP/3 bug I’m personally encountering in the course of completely casual use[1].
At the same time, you know what? I’m glad you suggested this, because I certainly didn’t think of it. Yes, in an ideal world, telemetry absolutely should be a separate process (or thread, or at least not share an event loop—a separate “hang domain”, a vat[2] if you want). And so should everything off the critical path.
I’m not saying Firefox is bad for doing it differently. I’m saying it’s silly that Firefox is forced to play OS to such an extent because the actual one isn’t up to its demands.
[1] https://github.com/ndilieto/uacme/pull/11
[2] http://www.erights.org/elib/concurrency/vat.html
Related posts
- Uacme: ACMEv2 client written in plain C with minimal dependencies
- Uacme: ACMEv2 client written in plain C with minimal dependencies
- Uacme: ACMEv2 client written in plain C with minimal dependencies
- Who should consider using BSD over Linux and why?
- Dehydrated: Letsencrypt/acme client implemented as a shell-script