James M Snell

`workerd` as it currently stands is not at all intended for multi-tenant environments ... specifically, it does not implement any mechanisms for ensuring the necessary sandboxing required for proper multi-tenant...

Disabling them makes sense but I'd still like to be able to bring them back optionally. Can we turn them off by default and have an option to show them?...

> The scariest thing to me is that we'd be going from a world where we have no compression to a world where (potentially) all websocket communication is compressed. Perhaps...

Fixed in #120

Thank you very much for the simple repro!

This issue has been fixed in main

@panva, if this was structured something like the following would it work for you? Using the worker ESM syntax only: ```js export default { async fetch(req, env) { return new...

Yeah, looks like we get this wrong. Unfortunately it'll need a compat flag to change. We should check all of webcrypto in case there are more of these and update...

> Maybe @jasnell has an idea how hard converting HTMLRewriter to use the high-level Streams API might be? Good question. Short answer is I don't know yet. Will have to...

Definitely agree with @kentonv here. `FileReader` doesn't really make a lot of sense in the workerd environment. Our `File` and `Blob` instances are always in-memory. `FileReader` wouldn't add much value,...