Home / Articles / The value of constraints / Versions / v1.1.0
The value of constraints: what changed in v1.1.0
From v1.0.0 (2026-10-16, 25f7ed3c9) to v1.1.0 (2026-10-27, db67c5ce1), paragraph by paragraph.
0 paragraphs added, 0 removed, 2 changed in place, 41 unchanged. About 0 words added and 71 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 cv-table.webp | images/ | Two constraints and what they take away: client-side encryption forbids the server from reading the data and removes the temptation to process there; open source, all of it, forbids private code and removes lock-in, the evaluation edition and building every customer's integration.it. | comparison
12 unchanged paragraphs, under In short {#in-short}, The mistake I made first {#mistake}, From the data to the keys {#keys}
!shot cv-keys.webp | images/ | Encryption on the client moves the problem from the data to the keys: a server that can read has to protect all the data, runs code next to it,keys, and puts the sovereignty line wherewith the data is; a server that holds ciphertext needs the keys protected, runs no code next to the data, and puts the line at whoever holds the keys.it. | comparison
27 unchanged paragraphs, under What it does not do: GDPR {#gdpr}, The biggest gain: nothing on the server {#server}, Open source, as a constraint {#open}…