@raphlinus I don't suppose you know what the right place would be to submit a proposal for a new Compression webapi? (so that the gzip required for server-gzip/WOFF or brotli required for server-brotli/WOFF2 can be made available to everyone, rather than be locked away)
-
-
Replying to @TheRealPomax
I think this level of standardization is IETF, which is why Brotli is an RFC (7932). But maybe I'm misunderstanding?
1 reply 0 retweets 0 likes -
Replying to @raphlinus @TheRealPomax
Oh, I think you're asking why compression is in neither the JS standard or as a Web API. I actually don't know the answer. But I think there might be some Web experts at the company you work for...
1 reply 0 retweets 1 like -
Replying to @raphlinus
I'm not, I'm asking how to go about putting in a proposal to add a "Compression" object to the already established Web APIs (e.g. audio api, gamepad api, fetch api, etc). Browsers already have _almost_ all the code in place, all they need is to expose zip/gzip/brotli.
2 replies 0 retweets 1 like
Right. I think there is a reason for this, but I don't know off the top of my head what it is, or who the right person is to ask. Best of luck!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.