Self-hosted, Self-Improving, Federated Everything App — dev management, agent orchestration, persistent mind, digital twin, second brain, and creative pipeline from a single dashboard over Tailscale to port the user into the OS
JavaScript ai-agentsdashboarddeveloper-toolsdigital-twinquantified-selfsecond-brainself-hostedtailscale
docs: describe the meatspace v2 content-key match accurately (#12432)
[._.]/ Adam Eivyf8931e304d5a
diff --git a/server/lib/schemaVersions.js b/server/lib/schemaVersions.jsindex 9a6daedfdc..24cc2546a3 100644--- a/server/lib/schemaVersions.js+++ b/server/lib/schemaVersions.js@@ -923,16 +923,16 @@ export const PORTOS_SCHEMA_VERSIONS = Object.freeze({// Rows without an `id` (logged before #8143) are still add-only: deleting// or moving one does not reach peers.//- // v2 (#12432): blood/epigenetic/eye rows merge by identity. A legacy row (no- // id, or the random id a pre-v2 reader stamped on it) is keyed by a- // content-derived `legacy-` id every machine computes alike, copies of one- // row resolve by per-row `updatedAt`, and a delete rides a top-level- // `rowTombstones: [{ id, deletedAt }]` list in the row's file. A v1 receiver- // must refuse that: its union keys a legacy row by its own random stamp, so- // every `legacy-` id would append a second copy of a row it already holds,- // and it cannot read tombstones or edits. v1 → v2 stays accepted: a v2- // receiver re-keys the v1 sender's random-stamped legacy rows (they carry no- // `createdAt`) to the same content id, so they match instead of duplicating.+ // v2 (#12432): blood/epigenetic/eye rows merge by identity. A row without+ // `createdAt` (an id-less legacy row, or one a pre-v2 reader stamped with a+ // random id) also answers to a content-derived `legacy-` key every machine+ // computes alike, copies of one row resolve by per-row `updatedAt`, and a+ // delete rides a top-level `rowTombstones: [{ id, deletedAt }]` list in the+ // row's file. A v1 receiver must refuse that: its union keys a stamped row by+ // its id alone, so a `legacy-` id would append a second copy of a row it+ // holds under its own stamp, and it cannot read tombstones or edits. v1 → v2+ // stays accepted: a v2 receiver matches the v1 sender's random-stamped legacy+ // rows by their content key, so they converge instead of duplicating.// An edit made on a v1 peer still arrives as a second row, as it always did.// Until a v1 peer upgrades it refuses the whole meatspace snapshot from a v2// peer, daily log included; the gap shows on the Instances page.