Home / Articles / Sixteen notes I did not want to lose / Versions / v1.1.0
Sixteen notes I did not want to lose: what changed in v1.1.0
From v1.0.0 (2026-10-13, 8654593cd) to v1.1.0 (2026-10-27, db67c5ce1), paragraph by paragraph.
0 paragraphs added, 0 removed, 3 changed in place, 46 unchanged. About 0 words added and 107 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
2 unchanged paragraphs
!shot sn-lane.webp | images/ | Send to my vault, from any browser. The reader's vault offersbrowser: a link offered three ways,ways that lets a URL,browser textwrite andto a QR code, carrying only where to write and the public key to encrypt with. Any browser, with no passkey and no sign-in, encrypts what it holds and appends it to the lane; it can writelane and never read. The next time the vault is opened with the passkey, the pane drains the lane into the reader's records. | architecture
21 unchanged paragraphs, under In short {#in-short}, What happened {#happened}, The nudge is working, for the right reason {#nudge}…
!shot sn-brief.webp | images/ | The brief in six steps, with what already exists beside each: the append lanes, the browser-side encryption the meter already uses, the drain the reply lane needs anyway,each, and the tests.little Onlythat the reader's key pair and the pane's link areis new. | playbook
12 unchanged paragraphs, under This stuff is hard in the real world {#hard}, And then there is email {#email}, Two config files, a new product line {#wire}
!shot sn-wires.webp | images/ | One pipeline, three wires. A wire is a vault plus a config:wires: the Industry Wire came first, andWire, the OWASP Wire and the AWS Wire were added on 13 October with two 17-line configs, the same builder and the same reader,Wire, each witha itsvault ownplus audiencea to find.config. | architecture
11 unchanged paragraphs, under What this does not claim {#limits}, Where this comes from {#sources}