1.6.0

Havemind 1.6.0

• Saving a local change is now a single write, so a crash or a full disk in
  the middle of a save can no longer leave a queued change half recorded.
• Large queued changes, such as a 25 MiB attachment, now wait in the device's
  local database instead of inside data.json.
• A corrupt sync state recovered from its backup right after the upgrade can
  no longer drop the list of files.
• The plugin moves its old file list over once on first start. Nothing to do,
  and no server change is needed. Devices on 1.5.9 and 1.6.0 sync normally.

Privacy: Havemind makes network requests only to the self-hosted server URL a
user explicitly configures for a vault. It contains no telemetry or analytics.

1.5.9

Havemind 1.5.9

• The plugin's sync state file no longer grows without limit. Extra copies of
  notes it used to keep forever are no longer made, and the ones a recovery
  makes are dropped after 7 days. On one device the file shrinks from about
  577 KB to about 110 KB, which makes every save lighter, phones included.
• Old copies already stored age out on their own within 7 days.

Privacy: Havemind makes network requests only to the self-hosted server URL a
user explicitly configures for a vault. It contains no telemetry or analytics.

1.5.8

Havemind 1.5.8

• Opening the app is faster: files that have not changed since the last start
  are no longer read and hashed again.
• Each edit uploads and stores half as much, and notes of roughly 250 to 490 KiB
  that used to be refused as too large now sync.
• Large attachments send and arrive about three times faster and use far less
  memory.
• An edit made while the plugin was still starting could be lost; it no longer
  is. An attachment deleted on another device is now deleted here too.
• Old leftover data in the device's local database is cleaned up.

Privacy: Havemind makes network requests only to the self-hosted server URL a
user explicitly configures for a vault. It contains no telemetry or analytics.

1.5.7

Havemind 1.5.7

• Restore in Activity now really restores: it puts the note back to the text
  it had at that change, as a normal edit that syncs.
• A change your device cannot apply no longer stops syncing. It is set aside,
  listed in the Havemind pane with Retry and Discard, and the rest keeps going.
• The status bar shows who last edited the open note. The old author colours
  overlay is gone.
• The owner can reject a device waiting to join. People no longer shows a made-up
  "connected" state.

Privacy: Havemind makes network requests only to the self-hosted server URL a
user explicitly configures for a vault. It contains no telemetry or analytics.

1.5.6

Havemind 1.5.6

• Conflicts: resolving one can no longer lose both versions, and a conflict you
  closed with "Keep both" can still be resolved later.
• The panel says why syncing failed. Sync now and Retry run one sync instead of
  rebuilding the connection, and Reset connection asks before wiping the pairing.
• A large or slow attachment upload no longer stops a device from receiving
  changes, and one stuck change no longer blocks the rest of the vault.
• Lighter on phones: far fewer reads and writes of the plugin's data file, and
  attachments are no longer kept in memory.
• Needs the matching server update for sessions that stay signed in past 30
  days and for attachments of 22.5 to 25 MB.

Privacy: Havemind makes network requests only to the self-hosted server URL a
user explicitly configures for a vault. It contains no telemetry or analytics.

1.5.5

Havemind 1.5.5

• Fixes phones and tablets that stopped receiving updates after another device
  changed an attachment such as a PDF. The device showed "offline" and never
  caught up. Updates now arrive normally.

Privacy: Havemind makes network requests only to the self-hosted server URL a
user explicitly configures for a vault. It contains no telemetry or analytics.

1.5.4

Havemind 1.5.4

• Fixes a device, typically a phone, that re-downloaded the whole vault every
  time Obsidian started and never received updates from other devices. Startup
  now downloads nothing unless the vault holds a local file sync does not know
  yet.

Privacy: Havemind makes network requests only to the self-hosted server URL a
user explicitly configures for a vault. It contains no telemetry or analytics.

1.5.3

Havemind 1.5.3

• Maintenance release. The test suite runs about 17 seconds faster; plugin and
  server behaviour are unchanged.

Privacy: Havemind makes network requests only to the self-hosted server URL a
user explicitly configures for a vault. It contains no telemetry or analytics.

1.5.2

Havemind 1.5.2

• Installation and update guidance now consistently directs users to the
  Obsidian Community directory. BRAT is no longer documented as a distribution
  path.

Privacy: Havemind makes network requests only to the self-hosted server URL a
user explicitly configures for a vault. It contains no telemetry or analytics.

1.5.1

release: 1.5.1, producer mappings carry metadata instead of file text

The plugin kept a second copy of the whole vault inside its own data.json:
every producer mapping stored the file's full text. Measured on a real pilot
vault, 8.4 MB of duplicate content in a 9 MB state document that Obsidian
rewrites on every state change. Compacted, that document is 0.6 MB.

Mappings now carry identity, path, hash and content kind. A legacy document is
compacted on load under the plugin data mutex. The text recovery needs comes
from its own durable journal, not from the mapping.

Rollback warning: a 1.5.0 client cannot read a compacted document. Do not
downgrade on migrated state.

Built from MikolajSapek/havemind 1.5.1 (main.js sha256 dc63121a0eb35725).
npm run verify: 2090 tests, 175 files, exit 0.