Join Nostr
2026-08-10 16:00:54 UTC

nostr-summary on Nostr: [ loblawbob873-svg/posterchanai ] "Lots of conflicts": the manifest's sha was the ...

[ loblawbob873-svg/posterchanai ] "Lots of conflicts": the manifest's sha was the ciphertext's, the scan's was the file's

A manifest entry's `sha` is the address of an encrypted blob — the hash of the CIPHERTEXT. A scan
reports the hash of the FILE. They were the same field, so the moment anything hashed, the engine
compared one against the other, never matched, decided the file had changed on both sides and did the
safe thing: kept both. A tablet joining a folder the desktop had filled duplicated every identical
photo it already had.

It was latent for as long as ordinary sweeps never hashed — size+mtime quietly carried it. Making a
first sweep hash, which a joining device genuinely needs, is what turned it into a conflict storm.
https://github.com/loblawbob873-svg/posterchanai/commit/3dfde20cf39d81f24c8a999b48f596f80a23080d