0.16.0

Two new features, and a fix for a reload bug that could leave two copies of the plugin syncing one vault. Upgrade the server first: this plugin needs trewd 0.15.0 or later, because it speaks protocol 5. Against an older server it says so and does not connect.

New

• Restore a folder to an earlier time. Right-click a folder and choose TrewSync: restore to an earlier time, or run Restore a folder, or the vault, to an earlier time for every note. Pick a date and time and press Preview: nothing changes until you have seen exactly which files would be put back and which made since would be removed. Restore applies exactly that preview on every device as one change, and Undo reverses it. Notes moved into the folder since stay where they are, notes moved out of it come back as a copy, and settings never change. If anything is saved between the preview and Restore, Restore is refused and asks for a new preview. See the plugin guide.
• Attachments on demand. In Manage this vault, choose to leave attachments over 1 MB (or 10 MB, or all of them) on the server. They download when you open a note that uses them, or tap them. Notes, canvases and settings always download. Free space removes attachments the setting covers from this device, each one first checked against the server and read back from it, and deleted rather than moved to the trash. Off by default, and per device. See the plugin guide.

Fixed

• Two copies of the plugin syncing one vault. Disabling, reloading or updating the plugin while it was still starting, most easily on a phone whose screen turned off at that moment, could leave the old copy syncing in the background with nothing able to stop it. On a test phone the old copy sent deletions of attachments the new one had just freed; they were restored from history. The old copy now stops for good when it is unloaded.
• After that happened once, every reload until Obsidian restarted showed the vault as not paired. It now starts normally.
• A changed setting is sent once it has been left alone for ten seconds, rather than on every save, so a settings tab that saves on each keystroke no longer fills the server's history.

Command-line client

trew 0.14.0 on npm speaks protocol 5 too, so it also needs trewd 0.15.0. A note a crash cut off part way through being replaced is put back at the next run instead of being sent to every device as a deletion.

Install

Update through BRAT, or download main.js, manifest.json and styles.css into .obsidian/plugins/trew-sync/ in the vault. Check them against SHA256SUMS, or with gh attestation verify FILE --repo waynehoover/trewsync.