2 Commits
Author SHA1 Message Date
waoziandClaude Opus 5.5 6f6d19f24d Rename account sync to Mesh
The codex-daochi-client-mesh-client-rename integration, committed as that
task staged it: mesh_client replaces daochi_client, account storage and
tests move to the Mesh names, and docs, locales and CI follow, with
existing accounts, encrypted records and local storage kept compatible.
The task stopped before its dependency versions were pushed; the next
commit moves Breeze to the pushed pins it needs.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-11-18 13:14:02 -03:00
waozi 14c57367d5 Keep each photo once in the account's private entity data, shared by every app
Diary and Photos keep their photos as records of the account's entity data
(Daochi docs/entity-data.md): entity.photos.<sha256>, synced as
private.entity.v1.photos in Inbe's own signed v6 sync and sealed in Daochi's
record profile with the account's photos key, the same bytes libsodium writes.
A photo's bytes travel as sealed chunks of at most 8 MiB at
/api/v1/blobs/entity/, so the same picture is stored once per node for every
app of the account.

Photos released versions kept move there by themselves: library photos once
their bytes are on the device, and Diary files that an entry includes, named
and dated as before. An old copy goes only after the sync node confirmed the
photo's record and chunks and they came back whole; then the old records name
the photo and keep every field for released versions, which read them through
2027-10-24, the Diary file leaves the device, hex chunks shrink, and the old
copies are deleted from each node. Any failure keeps the old copy for a later
pass, and a delegate device moves nothing.
2026-10-23 23:46:53 -03:00