Aqueous: The files you keep are compressed. Badly
Comments on “Aqueous: The files you keep are compressed. Badly”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Aqueous is a new public-domain archive format and archiver, aqr, that decodes the weak compression inside JPEG, PNG, MP3, ZIP and PDF files, recodes the contents with stronger models, and restores the original bytes on extraction. Its author reports that on Matt Mahoney's 10 GB benchmark, aqr produced 2.50 GB, against 3.70 GB for zpaq and 4.68 GB for zstd -3, at 61 MB/s compression. These figures are self-reported and not independently verified. Decoders ship inside the archive as WebAssembly modules.
Why it ranked
No. 16 of 43 with a score of 0.57. The panel rated it highest on new information (0.93) and technical depth (0.82), lowest on significance (0.54). Placed No. 16, No. 34 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- A new open-source archiver with lossless recompression, real benchmark data and a detailed technical design, though it is a single project release of moderate broader significance.
- AI judgeJudge 3gpt-5.6-luna
- A technically detailed release introduces a novel lossless recompression archiver, with reproducible benchmarks, architecture, format design, and implementation details. It is highly relevant to developers and infrastructure users, though real-world maturity and broad performance claims remain limited.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.57total under rubric v2.3
- Significance0.54
- Reader interest0.72
- Audience breadth0.56
- Practical relevance0.63
- Substantiated0.74
- Technical depth0.82
- New information0.93
- Counts against: Promotional0.22
- Counts against: Overclaim0.35
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.54 | 0.45 | 0.62 | 0.54 | 0.17 | +0.24 | +0.129 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.65 | 0.60 | 0.90 | 0.72 | 0.30 | +0.26 | +0.186 |
| Audience breadthHow many people who build technology does it concern? | 0.61 | 0.45 | 0.62 | 0.56 | 0.17 | +0.13 | +0.073 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.61 | 0.55 | 0.72 | 0.63 | 0.17 | +0.22 | +0.138 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.84 | 0.60 | 0.78 | 0.74 | 0.24 | +0.05 | +0.037 |
| Technical depthHow technically substantive is it? | 0.77 | 0.80 | 0.88 | 0.82 | 0.11 | +0.05 | +0.041 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.92 | 0.90 | 0.98 | 0.93 | 0.08 | +0.05 | +0.047 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.13 | 0.35 | 0.18 | 0.22 | 0.22 | −0.19 | −0.042 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.38 | 0.40 | 0.28 | 0.35 | 0.12 | −0.11 | −0.039 |
| Sum of contributions | +0.570 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.570 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-02/16/"><img src="https://rubric.hrih.si/badge/2026-11-02/16.svg" alt="Ranked #16 on Rubric, 2 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 1 matches source · 4 no source given · 3 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenBenchmark result
On Matt Mahoney's 10 GB benchmark (79,431 files, 10.00 GB of real-world data), aqr at level mid produced a 2.498 GB archive, compared with 4.68 GB for tar | zstd -3 -T10 and 3.70 GB for zpaq 7.15.
The article gives no link or citation for it.
The article says “aqr (level mid)2.50 2.498 GB · 164 s to compress, 38.8 s to extract”
The source says No source to compare with.
No source givenNumber
aqr compresses at 61 MB/s, including a round-trip check of every file, and extracts at 258 MB/s.
The article gives no link or citation for it.
The article says “aqr compresses at 61 MB/s, round-trip check of every file included, and extracts at 258 MB/s”
The source says No source to compare with.
Couldn’t checkBenchmark result
Compressed size over input size for JPEG is 0.778–0.794 with aqr versus 0.913 with zstd -3.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “JPEG 0.778–0.794 0.913”
The source says No passage could be compared.
Source cited by the article: github.com/lifthrasiir/aqueous/blob/main/docs/file-formats.md
Couldn’t checkBenchmark result
Compressed size over input size for SQLite files is 0.210–0.219 with aqr versus 0.366 with zstd -3.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “SQLite 0.210–0.219 0.366”
The source says No passage could be compared.
Source cited by the article: github.com/lifthrasiir/aqueous/blob/main/docs/file-formats.md
Couldn’t checkDate
The by-format ratios were measured on 2026-11-01.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Measured 2026-11-01; details in docs/file-formats.md”
The source says No passage could be compared.
Source cited by the article: github.com/lifthrasiir/aqueous/blob/main/docs/file-formats.md
Matches sourceFirst, only or fastest
ZPAQ put the decoder in the archive years ago.
The cited source says the same thing.
The article says “ZPAQ put the decoder in the archive years ago”
The source says “This does not break forward compatibility because the decompression code is stored in the archive”
Source cited by the article: mattmahoney.net/dc/zpaq.html
No source givenGeneralization
General-purpose compressors treat JPEG and ZIP files as noise and leave them alone, whereas Aqueous looks inside them.
The article gives no link or citation for it.
The article says “General-purpose compressors see a JPEG or a ZIP as noise and leave it be”
The source says No source to compare with.
No source givenCausal conclusion
Every file is decoded again and verified before the archive is finished, and extraction rebuilds the original bytes bit for bit.
The article gives no link or citation for it.
The article says “Every file is decoded again and checked before the archive is done”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 6 pts, not on front page
Recorded for context only, checked 2 Nov 2026, 05:46 UTC. It played no part in the ranking.