Skip to main content

Changes files

When there is no shared network, relay or folder - a colleague who gets a weekly update by email, a review copy for a lawyer, a board moving between two isolated networks - use changes files. A .deepstate-changes file holds every change to a board since the last one you exported; the recipient applies it and their copy catches up.

Not encrypted

Unlike every other transport, changes files are plain JSON. Anyone with the file can read it. Send them the way you would send the board itself.

Exporting changes​

Board select screen → Collaborate on the board → Without any of the above → Export changes file…. Choose where to save. The file name includes the board name and date.

  • The first export contains the board's entire history.
  • Each later export contains only what changed since your last export - DeepState keeps a cursor per board. If nothing has changed you're told so and no file is written.
  • The file includes changes made by anyone whose edits reached your device, not just yours, so a person on the relay can hand a complete update to someone who isn't.

Applying changes​

Board select screen → Apply changes… → pick one or more files. You can select several at once; they are applied oldest first.

  • If the board doesn't exist on this device it is created from the file.
  • If it does, the changes are merged with the usual rules (History & conflicts). Applying a file twice is harmless.
  • The result shows how many changes were applied, how many were skipped (already present or superseded) and how many are waiting - changes to a node whose creation hasn't arrived yet, which happens if files are applied out of order. Waiting changes are stored and applied automatically when the missing piece turns up.

Media​

Changes files carry the data of the board but not media files. Images and documents referenced by nodes will show as missing on the receiving side until they arrive by another route - typically a board export for the first handoff, which includes media, followed by changes files for updates.

Typical patterns​

  • Weekly digest to a stakeholder. Export changes every Friday; they apply each file in turn. Their copy is always a faithful subset of yours as of that Friday.
  • Two-way by email. Both sides export and apply. The cursors are independent, so A's export never includes what A received from B (that was B's change, and B already has it) - but it does include B's changes when sending on to C.
  • Bridging isolated networks. A device on each side with a shared USB stick: export on one, apply on the other, in both directions. For anything regular, a shared folder on the stick is less work.

Versus board export​

A .deepstate export is a complete snapshot with media, meant to give someone a board or move it between machines. A changes file is an incremental delta meant to keep two copies in step. Start with an export, continue with changes files.