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