Home / Articles / Messaging-FS / Versions / v1.1.0
Messaging-FS: what changed in v1.1.0
From v1.0.0 (2026-10-21, 4404c4a42) to v1.1.0 (2026-10-27, db67c5ce1), paragraph by paragraph.
0 paragraphs added, 0 removed, 2 changed in place, 79 unchanged. About 0 words added and 76 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 mf-vaults.webp | images/ | Messaging between two vaults.vaults: Each vaulteach has a lane for the other:other, Alicewhich encryptsits toowner Bobdrains, checks and writes to the lane on Bob's vault, Bob does the same into Alice's. Each owner drains its own lane, checks the signature, and commits the message to its own copy of the thread.commits. | architecture
28 unchanged paragraphs, under In short {#in-short}, Where we started: the inbox {#inbox}, The idea: a messenger between vaults {#idea}…
!shot mf-send.webp | images/ | One message, step by step.step: Alice encrypts to Bob's public key, signs with her own key, keeps a copy in her thread,Bob and writessigns, to Bob's lane. The server answers only "ok".and Bob lists and fetches with his enum key,fetches, decrypts, checks that the signature, the lane and the sender agree, adds the message to his copy of the thread, and marks it processed. | medium | architecture
49 unchanged paragraphs, under Messaging-FS and Email-FS {#fs}, Each vault writes only its own files {#owner}, Who sent it {#identity}…