#zstd
if the term "gzipped" is commonly used for data compressed with gzip then i propose referring to data compressed with zstd as "zestied"
May 19, 2025 at 7:34 PM
Okay, one more! Kite now supports zstd compression. It fetches the latest dictionary on startup, seamlessly handles dictionary updates, and it works without any new dependencies, instead relying on the OTP 28 `:zstd` module

tangled.org/jola.dev/kite
jola.dev/kite
An Elixir atproto Jetstream V2 subscriber library
tangled.org
September 21, 2026 at 2:24 PM
we have to do zstd compression over the wire
September 25, 2026 at 5:16 AM
but also,,,

gzip, all of y’all?

it’s 2026, Accept zstd already!

(lightrail included oops)
ever wonder who's doing sync1.1 backfill retries on repos that haven't been available to export? (but now areeeeee muah ha ha)
July 29, 2026 at 2:54 AM
64K zstd-q3-compressed content defined chunks should be enough for everyone – Bill Gates, probably
September 24, 2026 at 9:26 AM
klauspost/compress zstd in golang (with assembly in the Go style) now comes within 25% of Yann Collet's official C zstd implementation for decode speed/sec on arm64!
September 10, 2026 at 7:45 PM
Mildly impressive a 150gb mariadb database can compress to 12gb with zstd (using level 9). Really great for backups.
January 5, 2025 at 10:36 PM
sorry to whoever asked for a zstd-encoded compliment, I timed out reading what zstd is
April 21, 2026 at 12:05 PM
about to do a very boring demo! (which might be very interesting to a certain kind of person, several of whom i think will be there!)
April 29, 2026 at 8:44 PM
yes, but by default zstd uses a 64 kib window to construct its dictionaries, and 1 mib frames.
September 24, 2026 at 12:40 AM
New #golang compression release. Big features include #zstd concurrent stream encoding, arm64 decompression assembly and various minor changes.
July 1, 2026 at 11:14 AM
hey what if we made a ARM926EJ-S running at just over 200MHz do zstd compression. what if we
May 26, 2026 at 6:26 AM
higher compression above zstd-6 is enough but cpu over -6 holding me back from reaching 3k repos/sec exported over gigabit

tyranny of zstd
August 12, 2026 at 4:39 PM
okay here's another example of WIS vs INT. for months I've been on the warpath trying to reduce the amount of CPU I spend doing zstd decompression.

turns out, *compression* settings influence decode, and cranking *up* effort/window/frame size can actually give smaller, faster outputs to decompress.
WIS and INT are not the same thing. no one promised artificial general wisdom, only intelligence ;)
September 24, 2026 at 12:34 AM
make that

> compresses just over 2x better than CAR
and
> over 6x smaller than uncompressed CAR

if you go long with zstd-22
April 30, 2026 at 9:42 PM
And Klaus Post's compress module has hooks, docs, and an example for how to produce and consume them with Go's archive/zip!

pkg.go.dev/github.com/k...
zstd package - github.com/klauspost/compress/zstd - Go Packages
pkg.go.dev
September 9, 2025 at 2:32 PM
Steam is working on adding zstd compression for game chunks (every game file is split into 1MB), it currently uses LZMA.

Wonder how much of an overall improvement it will be.
February 17, 2025 at 5:55 PM
*compresses you with zstd*
March 11, 2026 at 10:15 AM
New v1.18.4 release of #golang compression library adds zstd compression to gzhttp middleware. Also zstd can now have some options modified on reset. See more at: github.com/klauspost/co...
February 9, 2026 at 8:38 AM