6cy
Experimental streaming archive format with per-block codecs
Details
- External ID
- 47049743
- Source
- HN
- Company
- —
- Product
- 6cy
- Website domain
- github.com
- Launched
- Feb. 17, 2026
- Cohort
- —
- Upvotes
- 35
- Upvotes percentile
- 0.7634770889487871
- Tags
- —
- Fetched at
- Sept. 7, 2026, 9:25 p.m.
- Updated at
- Sept. 7, 2026, 9:25 p.m.
Description
Hi HN,I’ve been experimenting with archive format design and built 6cy as a research project.The goal is not to replace zip/7z, but to explore: • block-level codec polymorphism (different compression per block) • streaming-first layout (no global seek required) • better crash recovery characteristics • plugin-based architecture so proprietary codecs can exist without changing the formatRight now this is an experimental v0.x format. The specification may still change and compatibility is not guaranteed yet.I’m mainly looking for feedback on the format design rather than performance comparisons.Thanks for taking a look.
Enrichment
- Theme
- AI video generation and ComfyUI tools
- Vertical
- Horizontal
- Function
- Data infrastructure
- Audience
- Developer
- AI stance
- Not AI
- Project type
- Hobby / open-source project
- Normalized one-liner
- streaming archive format with block codecs
- Manually corrected
- False
Could you build this?
No Designing an experimental streaming binary archive format with block-level polymorphic codecs and crash recovery requires deep knowledge of compression algorithms, binary protocol design, and low-level memory/IO management.
What it would actually take: The implementation requires designing a custom byte-level binary container specification with framing, CRC/checksum verification, error-correction headers, and dynamic codec negotiation per block (supporting algorithms like zstd, lz4, brotli, or custom entropy encoders). The hard parts are proving zero-seek streaming correctness, crash resilience under truncated bitstreams, and optimizing memory throughput via zero-copy I/O in C, C++, or Rust. It demands advanced expertise in information theory, data compression, and low-level systems engineering.
Discussion
8 comments analyzed.
Concerns raised: No public benchmarks or side-by-side performance comparisons with other tools, u8 codec ID limit could cause collisions with many external codecs
Feature requests: Advertise required codecs early in stream for fast failure detection, Use UUIDs for external codec identifiers instead of u8, Share methodology and raw benchmark numbers publicly
Competitors
Other products that read as similar to this one — 41 launches clear the similarity bar, closest 8 shown.
Attention rank: #7 of 42 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).
Launched 86 days after the earliest competitor.
- See · hn · 2026-02-21 · 5 upvotes · similarity 0.42
- I successfully failed at one-shot-ing a video codec like h.264 · hn · 2026-04-04 · 9 upvotes · similarity 0.42
- Optimind compress and Archiver · ph · 2026-09-17 · 2 upvotes · similarity 0.40
- Lossy Compression Conserving the Physics · ph · 2026-09-18 · 1 upvotes · similarity 0.39
- TurboBench, the Compression Lie Detector, 100 Codecs, Daily Update · hn · 2026-09-16 · 5 upvotes · similarity 0.39
- Overfitted a 900KB Transformer to Compress a 100MB CSV into 7MB · hn · 2026-06-23 · 112 upvotes · similarity 0.37
- misa77 · hn · 2026-07-15 · 164 upvotes · similarity 0.37
- ExANS · hn · 2026-08-05 · 15 upvotes · similarity 0.36
Other launches for this product
- No other launches for this product.
Same idea, different domain
Nobody's really built a data infrastructure tool for Media & entertainment yet.