rusty_zstd — Pure-Rust Zstandard With No C And No Copyleft
rusty_zstd is Zstandard in Rust: a pure-Rust RFC 8878 compressor with zero deps, no C, no FFI, and no copyleft on the wire format you already use.
Zstandard is the compressor the modern internet actually picked. Logs, snapshots, container layers, SpaceDB payloads — if the bytes are big and the CPU is cheap, someone put zstd on the wire. The format is IETF RFC 8878. The reference implementation is C, and a lot of "Rust zstd" is still FFI into that C.
rusty_zstd is Zstandard in Rust: a pure-Rust RFC 8878 compressor with zero dependencies, no C, no FFI, and no copyleft. That last clause matters. The format is open. The usual C library is not a license you want at the bottom of a mesh node. rusty_zstd is the Remade with Rust remake. The catalog is Remade with Rust. The thesis is rebuilding the foundation of the internet. This article is the compressor.
Why rusty_zstd Is The RFC 8878 Compressor Without C
A compressor touches untrusted bytes. Frames, windows, dictionaries, literals — the same parser shape as a codec, the same CVE class. The NIST Secure Software Development Framework keeps pointing at memory-safe languages for exactly that work. Binding libzstd adds a Rust type in front of the same heap. rusty_zstd deletes the heap.
Zstandard in Rust that still needs a C toolchain fails the house test: ship onto a machine you do not own, including wasm32, with no clang. An RFC 8878 compressor that is also copyleft-encumbered fails the Incentive test. rusty_zstd fails neither.
Trust, Security, and Incentive apply to compression the moment the payload is someone else's snapshot. Trust that the frame is the format the RFC named. Security that the decoder is rusty_zstd, not another C window. Incentive that Zstandard in Rust is permissively licensed so a builder can embed it next to SpaceDB without a license review that lasts a quarter.
What rusty_zstd Ships As Zstandard In Rust
github.com/Remade-With-Rust/rusty_zstd is the source. Zero deps. No C. No FFI. No copyleft. The wire is RFC 8878. That is the whole pitch, and it is enough, because every other zstd story in Rust is a compromise on one of those five.
rusty_zstd Speaks RFC 8878, Not A Private Frame
An RFC 8878 compressor that invents a sibling format is a science project. rusty_zstd compresses and decompresses Zstandard as the IETF published it. Interop is the product. Zstandard in Rust that cannot open a zstd frame from the C encoder is not a remake. It is a new format with a familiar name.
The IETF RFC 8878 text is the oracle. rusty_zstd is the memory-safe implementation. That split is honest.
No C, No FFI, No Copyleft In rusty_zstd
Zero dependencies is a Security choice. Every crate you did not add is a crate Deputy does not have to vault. No FFI is a deploy choice: wasm and ESP do not get a CMake surprise. No copyleft is an Incentive choice. The EFF has argued for decades that a free internet needs infrastructure you can embed without asking permission. rusty_zstd is that argument for the compressor.
Zstandard in Rust with a GPL-shaped surprise at the bottom gates who can ship. rusty_zstd does not.
Where An RFC 8878 Compressor Sits In The Stack
SpaceDB replicas, Disco chunks, media sidecars, model manifests — anything that used to call zstd now has a Rust path. A distributed cloud that compresses with libzstd still has a C toolchain in the story. rusty_zstd is how Zstandard in Rust becomes the node default.
AI on the edge downloads weights. Those blobs are huge. An RFC 8878 compressor that compiles into the same binary as Candle is how the download stays in-process.
How rusty_zstd Feeds The Distributed Cloud
Disco Party places sealed chunks on machines nobody owns centrally. Those chunks are compressed. rusty_zstd is the RFC 8878 compressor that keeps that path memory-safe.
Trust The Frame, Secure The Window
Trust is a frame that matches RFC 8878. Security is rusty_zstd — Zstandard in Rust with no C window to overflow. Incentive is zero deps and no copyleft, so the safer path is also the path legal will sign. The NIST Zero Trust Architecture tells operators to stop trusting the perimeter. rusty_zstd is how you stop trusting the decompressor as well.
The Electronic Frontier Foundation has documented how "the data stays encrypted" claims collapse when the helper library is the old native one. Compression sits under encryption. Get it wrong and you have a parser bug next to a key.
Mesh Nodes And The Freedom Guide
The Freedom Guide is local-first steps. Local-first that still needs libzstd is local in theory. rusty_zstd is Zstandard in Rust so a vault backup and a SpaceDB replica speak the same RFC 8878 compressor. Era 1 stores the sealed blob. Era 3 ships work products that should not inflate a data-center bill to move.
Privacy Rights Clearinghouse catalogs what leaks when "we compressed it in the cloud" was the architecture. rusty_zstd lets the architecture be "we compressed it here."
The Catalog Entry For rusty_zstd
Source is github.com/Remade-With-Rust/rusty_zstd. Cards and shipping status live on the Remade with Rust catalog. The mesh this RFC 8878 compressor feeds is what a distributed cloud is and the Disco Party. Digital Freedom is Trust, Security, and Incentive.
If you came from the Learn index looking for Zstandard in Rust, this is the crate. If you came from libzstd, this is the remake. No C. No FFI. No copyleft. The internet you want to own still shrinks its bytes. rusty_zstd is how that sentence stays true without the C.
The allocator this compressor sits on is rusty_alloc. Structured documents in the same rebuild family are rusty_xml. Fetch-by-hash instead of a rented bucket is content-addressed storage.