HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
cyphar
paperback
Rust2018–2026
cyphar / paperback

paperback

Paper backup generator suitable for long-term storage.

11Distinct people
18Mentions
0Explicit recommenders
1.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Paper backup generator suitable for long-term storage.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year18 dated mentions

Observed mentions: 2018-11-21 03:21:35 UTC to 2026-05-27 19:15:50 UTC.

012342018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC312
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC312
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC303
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC303
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC404

What Hacker News says

18 sources
I've experimented with this using one of the commercial print-on-demand services. Not filament, a binder-jet sintering marine stainless steel type of process, IIRC. Slightly modified Noto Sans Extracondensed font with... Let me check the files... 0.1mm line width, 0.45mm lower-case "m" width, dense letter and line spacing, gets 3KB ASCII per square inch. ...Engrave, don't emboss, or the letters will come off with impact and corrosion! Filling the engraved letters with black wax makes it optically legible under a good handheld magnifying glass. Then rub with vaseline/mineral oil/wax/ACF-50, mount on a brass holder (check relative galvanic corrosion order!), store pressed against aluminium or zinc sheet sacrificial anodes Just In Case(TM), inside polyamide or ABS case. Should last basically forever. I designed it for manual reading, so the
Read the rest
holder doubles as the "reader". Basically just a spindle going through a hole in the disk, holding a margin in the edge and center of the disk. The text is a spiral, so you can spin the disk to help keep the viewed region aligned under a higher-power microscope. For home printing, probably the way to go is Formlabs wax resin (or equivalent), then either learn brass casting yourself or hire a jeweller to do it. Though you won't get as good resolution/density as the metal process I tried. And really, laser engraving'll probably be cheaper and better. Consider if good-quality paper and ink, maybe laminated, inside a Pelican case'll be more practical. I wouldn't personally trust any of the common plastic printing materials to hold up for important data under oxygen, UV, fatigue, heat cycles. Are you sure the resin's not overcured or undercured, the filament fused correctly and won't delaminate, it won't reach the glass transition temperature during summer? And bacteria is already evolving to eat plastics. Maybe SLS/MJF polyamide's okay, but in that case, I'm not sure I'd trust the sintered structure for small details (and they don't have great resolution anyway). > The assumption was that using common 3D printer measurement tools (like for bed-leveling) would provide a way to read back whatever data was encoded onto the surface. > And then, obviously, if that proof of concept exists, I'd wonder about some kind of advanced version that used specialized equipment for the reading (and possibly the writing/printing). At these small amounts of data, specialized read hardware just adds risk IMO. Plain text can be read manually or with OCR. QR codes can automate reading with a standard flatbed scanner or smartphone camera. Consider ideas for encoding: Plain text, B64, hex, Reed-Solomon codes... 1-bit depth structure turns most of 3D printing's storage density into redundancy, but anything truly 3D adds read risk. If you insist on automating reading, QR codes will get you error correction, encode/decode software, and COTS hardware for "free". Personally I think human readability is a big advantage too. Maybe OCR text, and put error codes in a QR beside the text for byte-perfect computer input? Compare: Memory of Mankind uses ceramic tablets in a desert cave. Arch Mission Foundation project uses holographic glass. Long Now Rosetta Disk engraves with electron beam on nickel, IIRC was/is also commercially available for personallized jewellery. M-Disc and Bluray (HTL?) have modern digital storage density, good stability, work with commodity hardware. ...See design considerations of prior art for digital storage in 2D, naïve 3D version is to just use these as a heightmap: - https://github.com/cyphar/paperback - https://github.com/za3k/qr-backup/ - https://github.com/colindean/optar - https://github.com/Sjlver/psst - https://github.com/schroeding/paperstorage - https://github.com/intra2net/paperbackup Also, don't sleep on the centuries of work done by archivists and historians! The top comment is right; acid-free archival paper has very good overall cost, density, stability.
In Ask HN: Are there examples of 3D printing data onto physical surfaces?
There are much better systems for splitting data than just chunking it into N chunks, the most common is Shamir Secret Sharing[1] (the main benefit being that you can construct an M-of-N scheme easily and having N-1 shards provides you zero information about the secret). One word of caution -- a lot of software developers get enamored by the idea of information-theoretic security when they first run into it, but you eventually realise that useful applications of tools like SSS are actually quite rare. Shameless plug: I wrote a project a few years ago to create PDF-based backups with sharded keys which would do exactly what I suspect you want[2], unfortunately I got stuck at the "make a nice UI for it" stage (everything works but it's just a CLI tool at the moment). I guess I should take a look at using an LLM for that these days... (I use
Read the rest
d this to store my password manager root password and necessary keys to pull and decrypt the encrypted backups of my server.) [1]: https://en.wikipedia.org/wiki/Shamir%27s_secret_sharing [2]: https://github.com/cyphar/paperback/
In Show HN: If you lose your memory, how to regain access to your computer?
Yes. QR codes are meant to store only a few kilobytes at most. They are not suitable for encoding gigabytes of data. At perhaps 2KB per page, you'd need 524288 pages to store a 1GB. That's 1048 reams. Please just use an archival optical disk instead. Even if the scheme using multiple QR codes in sequence rather than a single large code block. The paper backup implementations that use QR codes https://github.com/intra2net/paperbackup https://github.com/cyphar/paperback are only meant to be used for private key backup.
In Ask HN: QR Codes Unsuitable for Storing Gigabytes and Beyond in Graphic Format?

Showing the 15 most recent of 18 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.