NodeSpace Sync 0.1.5

DRAFT, written 2026-10-22 before anything is released. Edit to match the final build; remove lines for anything that does not ship.

Sync 0.1.5 (since 0.1.4)

• If another device deletes a note you had edited, the text you pushed is kept on your device and saved in Saved copies until you delete it there.

• A note you re-create with the same id after deleting it no longer gets deleted again by an old pending delete.

• AI chats stay private: a chat is never sent until your workspace is fully set up for private chats, and Sync AI chats is on.

• Mentions that point to a note that arrives later are now created when that note lands.

• Conflict clean-up is safer: if a note changes while a deleted folder is being removed, the removal waits and retries, and the text of removed notes stays in Saved copies.

• The in-app "a newer version is available" notice follows the build's sync host and re-checks every six hours.

• Under the hood: the workspace's person and collection notes use new Sync types (sync-person, sync-collection); the cloud accepts both names, so devices on 0.1.4 keep working.

• The app no longer keeps its own copies of the background service in ~/.nodespace/bin; it uses the installed one, so opening the app does not restart it.

Updating: 0.1.4 has no update notice, so install 0.1.5 by downloading the installer once. From 0.1.5 on, the app shows a "newer version available" banner with a Download button. Going back to 0.1.4 after running 0.1.5 is not supported (the new person and collection types are unknown to 0.1.4).

Needs: cloud migration 26 (applied on the dev workspace). Core v0.3.9.

Known limits: "Total nodes" can differ by one between devices; an import's mentions are not sent to the cloud yet; the cloud does not keep deleted note text for recovery yet.

Core: v0.3.9. SHA-256 of NodeSpace-Sync.pkg: 32d30f0a7cc5f01337e781b42f474f916580182f64d8fa52f0342d8f6053cb75

NodeSpace Sync 0.1.4

NodeSpace Sync 0.1.4

This release is about not losing your work when several devices change the same notes, and about making sign-in steadier. It needs two database updates on the Sync cloud (migrations 24 and 25); they are already applied on the development workspace.

Your notes are safer

• An edit you made offline is no longer overwritten by the old text when another device only moves the note. The edit and the move both survive.
• When two devices disagree about where a note belongs, the later real move wins, even if the other device only re-ordered it afterwards. A move that failed to reach the cloud is sent again, and a note no longer ends up under two parents after an offline move.
• A note you deleted stays deleted when an older copy comes back from the cloud, including when a live update arrives first. A delete that the cloud refused brings the note back instead of leaving the two sides apart, and a delete that could not be sent right away is retried.
• If another device deletes a note that you had edited, the text of your edit is kept in Saved copies. The Saved copies list no longer fills with notes you never touched (a 500-note removal used to add 500 copies).
• Renaming a collection now settles on one name on every device. With migration 24 the most recent rename wins, whoever created the collection.
• A large import (10,000 notes) now arrives with all its nesting intact on your second device, and the catch-up backs off politely when the cloud is busy instead of retrying every 15 seconds.
• Contacts (people you typed in who are not members) now sync to your other devices as plain notes. They are never shown as workspace members.

Sharing and who can use a collection

• A lock beside a collection in the sidebar opens "Who can use this collection". You see each person with their level (Admin, Editor, Viewer), and you can change a level, remove someone or add a workspace member. The last admin of a collection cannot be removed or demoted by mistake.
• "Open to everyone" makes a collection usable by the whole workspace. It asks first, because the list of people and their levels are cleared.
• Refusals are explained in plain words.

Sign-in

• Sign-in tokens are refreshed directly with the sign-in provider. A busy moment or a short outage no longer signs you out; only a refusal that really means "sign in again" does. Signing out always ends signed out, even while the first catch-up is running.

No more "Default Collection"

• The built-in "Default Collection" row is gone. Notes with no collection simply sit at the top level. Migration 25 removes the row from the cloud. Devices still running 0.1.3 keep working, but they put an empty "Default Collection" row back (it is harmless and disappears when you update).

Requirements

• Cloud migrations 24 and 25 must be applied on the workspace. Without them, renames do not follow "later wins" and 0.1.4 cannot file notes without a collection.
• Based on NodeSpace core v0.3.8. The installer works over 0.1.3 and keeps your notes.

Known limits

• When the device that pushed an edit loses it to another device's delete, that device does not get a Saved copy (the deleting device does). Needs a cloud change.
• A few clean-up items in the conflict journal and one pending-delete corner case (re-creating a note under the same id) are still open.
• No in-app update notice yet; download the installer again to update.

Core: v0.3.8. SHA-256 of NodeSpace-Sync.pkg: ad5187ffe4788b667d6c68c78dd065aaa23126effabb24b2ab37d718041ba21f

NodeSpace Sync 0.1.3

NodeSpace Sync 0.1.3 (core v0.3.7). SHA-256: d9580e4ba75c4aa37a3164189be71c554ef622bf4f5f02a5c31657b7c53ac218

NodeSpace Sync 0.1.2

NodeSpace Sync 0.1.2 (core v0.3.6). SHA-256: a144c4238ce08315f7d9dae3cebf9297cfba03e9948198c2552d74211c0cdf02

NodeSpace Sync 0.1.1

NodeSpace Sync 0.1.1 (core v0.3.6). SHA-256: 3d0b310494700b3e2df5604a41f97e77641d5d8a87b8a3e016711b75aad153b9

NodeSpace Sync 0.1.0

NodeSpace Sync 0.1.0 for Apple Silicon Macs. Signed and notarized by Apple. SHA-256: add12b396c0f6c9ae96a9121bd0ac026ee9d293c32ae36a920f76f1b928c8f8f