github.com/s4wave/spacewave

Spacewave 0.57.27 moves all local storage to a new single-file database on desktop and to a new storage format in the browser, fixes lost file data in shared Spaces, and makes devices reconnect more reliably.

Features

• The browser keeps its local data in a new storage format, on OPFS or, where that is unavailable, IndexedDB. Data a browser saved before this release is not opened, so the browser starts with empty local storage. Spaces held in Spacewave Cloud or on another device download again; data that existed only in that browser is not carried over.
• Desktop and command-line storage now uses s4db, a new database that keeps each volume in one file. Several Spacewave processes can share a volume safely, and readers never wait on a writer.
• Existing desktop and command-line volumes convert to s4db in place the first time this release opens them. The conversion keeps the volume's identity and data, checks that every key and value matches, and needs free disk space equal to the volume. A crash during conversion leaves the old file, which converts on the next start.
• The Badger storage engine and the --badger-db option are removed.
• The command line can repair lost Space data on a stopped device: spacewave debug payload-restore rebuilds a lost file payload from its source, and spacewave debug ref-repair restores the block links that storage cleanup relies on.
• Forge now names the plugin a waiting Execution needs.
• A Git remote URL can name its session, as in spacewave:///u/2/so/<space>/-/<object-key>, so a remote on a session other than the first needs no --session-index.

Fixes

• Files written into a shared Space could lose their content on other devices: storage cleanup removed data that replaying the Space still needed, and replay stopped with "block not found". That data is now kept as long as replay reads it.
• Two devices could stay disconnected after one of them restarted, until one restarted again. A lost connection offer is now sent again until it is answered, and a device follows the signaling service across reconnects.
• A device linked to a Space from the command line was not offered as a Forge worker, because its setup never finished. It now reaches the ready state.
• A returning browser visit after a release no longer starts Spacewave twice, and a single failed network request no longer makes it fall back to the cached release.
• A browser out of storage now shows "Storage full" in the sync status, with the number of Spaces it cannot store. Before, the copy of a newly linked account retried silently and looked as if it was still copying.
• A second browser tab could fail to load, because the first page looked closed to the ServiceWorker. A page now registers with the ServiceWorker only after it can show that it is open.
• The command line now logs a warning when the connection to Spacewave Cloud stops retrying, since cloud updates then stop until a restart.
• A plugin that fails at start now waits longer between restarts, up to five minutes, instead of restarting about once a minute forever.
• Plugins running in the QuickJS host can use crypto.getRandomValues, and have a larger stack.
• git push --force-with-lease to a Spacewave Git remote now works. Before, the remote refused the push.

Improvements

• Saving a change to a Space takes one storage commit instead of five, and checking a Space's history verifies only new changes.
• A device catching up on a Space resumes where its last pass stopped instead of replaying the Space's history each time.
• The browser caches each plugin's files, so a returning visit no longer downloads them again.
• The billing page groups subscription management under Plan and lays out extra storage spending more clearly.
• Buttons and form fields across the app have accessible labels and native semantics, and external links open without access to the app's window.
• A long replay logs its progress every 30 seconds.
• Saving a change to a large Space writes only the history added since the last save, instead of rewriting a record of all of it each time.
• s4db reads its index in key order and caches about 40% more of it in the same memory, and rebuilding a large volume no longer takes time and memory that grow with the square of its history.
• Storage cleanup checks only removed links before it records a change, which halves the index reads of copying a Space to a new device.

Downloads

MacOS (arm64) | Windows (amd64) | Linux (amd64)

Spacewave 0.57.26 makes Spaces more reliable when a device is missing data, adds a way to open one Space in a local browser window, and speeds up saving changes.

Features

• The command line can now open a single Space in a browser. spacewave web --space <id|name> serves that Space from your device as a read-only view, with no download of the browser runtime. The view reconnects after the Spacewave daemon restarts.
• spacewave space trim now shows how far a Space's history can be trimmed on this device. It reports the checkpoint, the changes waiting above it, and whether this device still needs to acknowledge.
• Space owners can now remove writers that have stopped syncing from the trimming group with spacewave space roster, so the Space can trim history those writers have not caught up on. A removed writer returns once it catches up.

Fixes

• A Space that is missing a file or data block now stays open instead of repeatedly restarting. It shows everything before the missing change, and it resumes from that change once the data arrives.
• A device that was catching up on a Space could fail to acknowledge changes, which stopped the Space from trimming its history. Acknowledgment now continues while the device catches up.
• New devices joining a Space could stop partway with a "block not found" error. This happened after a file was appended and its content was cleaned up too early. The content is now kept until every device has read it.
• A device copying an account's data no longer retries over and over when no connected device has the data it needs. It waits until another device connects or the Space changes.
• A device that was refused a connection, or had its link revoked, now sees the reason the connection closed. Before, it saw only "stream reset".
• Errors about missing Space data now name the file or change involved, which makes lost data easier to track down.
• Command-line options such as --remote-daemon can now be placed before the command, as in spacewave --remote-daemon <peer>@<addr> space list. A usage error now prints to the error output only.

Improvements

• Saving changes to a Space is faster. Committing a change now takes three storage writes instead of seven, and storage cleanup runs in larger batches.
• Catching up on a Space is faster and uses less storage activity, because each pass now saves its changes together instead of after every change.
• Opening a Space from the command line and reconnecting after a restart no longer requires the browser runtime.

Security

• When a device's access changes, links already open to it are now rechecked, and links from devices that are no longer allowed are closed, including open remote shells.
• The read-only Space view in the browser allows only read requests. Each request is checked against the bound Space and Session.

Downloads

MacOS (arm64) | Windows (amd64) | Linux (amd64)

Spacewave 0.57.25 adds command-line tools for linking devices of the same account, fixes sign-in after logging out, and makes release updates and shared local storage more reliable.

Features

• The command line can now link another device to a Session. spacewave session pair issues a pairing code, shows the login pair command to run on the other device, and approves the device after the emoji check. Add --yes to approve without the prompt when scripting.
• A Spacewave daemon can now be reached directly from another Session of the same account. Run spacewave serve --udp-listen host:port on one device, then pass --remote-daemon <peer-id>@<host:port> to any command on another device. The Session key never leaves the device that holds it.

Fixes

• Logging out and then signing back in to the same account now works. Before, the old Session could stay active and block the new sign-in.
• session pair now prints the ID of the Session that was actually linked, and session revoke accepts that ID. Before, it printed a temporary pairing ID, and revoking that ID reported success while leaving the linked Session in place.
• session revoke now works for local accounts, which have no password or passkey, and refuses IDs that are not a Session or paired device of the account.
• A command run against the device's own Session now fails immediately instead of hanging.
• Long-running copies of Spacewave now keep following published updates. Before, content changed by a release could fail to load until you restarted the app.

Improvements

• When several Spacewave processes share the same local storage, a process waiting for its turn to write now resumes as soon as the other process finishes, without a fixed delay between checks.

Security

• Remote shell access now requires the connecting device to be signed in to the same account. Devices from other accounts that happen to share a Space are refused.
• Direct device-to-device connections between Sessions are admitted only for active, unrevoked Sessions of the same account.

Downloads

MacOS (arm64) | Windows (amd64) | Linux (amd64)

Spacewave 0.57.24 frees cloud storage held by deleted data and fixes Git pushes that could wait forever.

Fixes

• Git pushes to a Space and Git LFS uploads now wait only for that Space's uploads, so a push no longer hangs while another Space is syncing.
• Quitting the desktop app after reopening its window now exits cleanly.
• Plugin tasks interrupted by a plugin reload now resume instead of failing, and tasks left behind by a restart now finish or cancel.
• Signing up for email updates on the blog now sends one request.

Improvements

• Cloud Spaces now free the storage of data that is no longer referenced. A device holding a complete copy of a Space marks unused storage for removal, and the storage is removed a day later, after any data still in use is copied out.
• Released versions of Spacewave now free the storage of replaced files after each publish.

Downloads

MacOS (arm64) | Windows (amd64) | Linux (amd64)

Spacewave 0.57.23 adds Space controls for edit syncing, group decisions, and offline storage, while improving sign-in, invites, file storage, and reconnection reliability.

Features

• Space settings now let you choose whether edits merge or follow one order, including selecting or replacing the main device.
• Space owners can hand control to the group, where membership and settings changes require agreement from more than two thirds of members.
• Each device can download items on demand or keep the whole Space available offline. The same choice is available when joining a Space.
• New command-line tools create and accept invites, list and remove Space members, and manage whole-Space downloads.

Fixes

• Repeat browser sign-ins now reconnect the account’s existing Session correctly.
• Invites can now be accepted after an account change.
• Spaces now catch up on changes made while they were closed, and Space lists refresh when access changes.
• File uploads no longer hang, file renames resolve their destination correctly, and file watches recover after a released lookup.
• Peer connections now recover when the remote device restarts.
• Git Spaces now reuse retained local repository data, and Git LFS reports startup failures instead of silently failing.

Improvements

• Sign-in handoffs now finish on one confirmation screen with a direct option to continue in the browser.
• Space settings show who controls the Space, changes waiting for group agreement, and edits waiting to be ordered.
• Command-line Session lists now show usernames, and Space commands can resolve Spaces by name.

Security

• Command-line account changes can now be authorized with a passkey.
• Removing Space members rotates access so removed members cannot read future changes.

Downloads

MacOS (arm64) | Windows (amd64) | Linux (amd64)