Felix Handte

@kravietz, that's true, in the sense that all LZ-style compression of HTTP responses are vulnerable to BREACH. I don't believe Zstd has any features that make it any more or...

@kravietz, aha, I missed that detail. Makes sense.

Thanks! @tokers, in short, yes. Though we anticipate standardizing a set of dictionaries, rather than a single one (e.g., one for CSS, one for JS, one for HTML, etc.). Note...

To clarify, it's a body content encoding. The content-coding identifier is `zstd`. It's been standardized in [RFC 8478](https://tools.ietf.org/html/rfc8478). It's supported by some non-browser clients and servers (which I guess is...

Hi @andrew-aladev, In general, using a dictionary with Zstd is entirely optional, you don't need one. And in fact, the HTTP extension specified in the above-linked RFC, the `zstd` content-coding,...

@andrew-aladev, I would hesitate to generalize a specific experience you've had into a global statement about one compressor being universally better than another. Compression is notoriously tricky that way--the specifics...

@kdave thanks for flagging this. @Natrox, awesome! @terrelln is the relevant authority for this stuff, so we should defer to him. He's out on vacation at the moment, but I'll...

Hi @jreiser, Zstd has a couple existing mechanisms to support these scenarios: ### [Static Contexts](https://github.com/facebook/zstd/blob/v1.5.2/lib/zstd.h#L1539-L1564) These functions allow you to construct a zstd context that will only use the provided...

@jreiser, > But doesn't a dictionary make a third call? You're right, if you load a dictionary into the context, that may or may not internally trigger the creation of...

Hi @thesamesam, Thanks for reporting! I'm happy to add an exclusion for this platform if you tell me how to recognize it. Is this specific to Gentoo, or would it...