features / privacy
what a solstone app takes in waits on that device until your journal confirms it holds each file. only then is the copy removed. anything your journal hasn't confirmed stays put and goes again later.
the device and your journal compare each file by its fingerprint. your journal reports on every file, and the device checks its own copy again before removing anything.
each file is fingerprinted with SHA-256 on the device. your journal checks every file against its fingerprint before it writes it if it can, and reports on each file with one of three states: written, already_held (it had this exact file already) or received_not_written. only the first two let the device remove its copy, and before it does, the device checks that its own file still matches the fingerprint it sent.
a quick check that a file looks unchanged is used to decide what to send, and is never treated as proof that the journal holds it. a connection that succeeds, an upload that finishes and an answer that never arrives all leave the copy where it is.
every solstone app follows the same rule. where the device brings something of its own, it's here.
resolve.rshow your journal checks each file and chooses its answerIngestAcknowledgment.swifthow the solstone app for mac reads the answers before it removes anythingTransferEngine.swiftthe same on iphone and ipadWatchRelaySender.swiftthe watch's hand-off to the phoneSegmentDrainer.ktandroid's sender, and how waiting material follows your pairing