1.0.46
7th November, 2026
P2P synchronisation can stop connecting when our devices are on different versions. And this is one of those versions.
If we use P2P synchronisation, let us make sure all our devices are on the same version.
Fixed
Synchronisation and recovery
- Receiving devices no longer reject newly saved files with 'seems to be corrupted! Writing prevented' because rapid edits left the sender's cached file size out of date. New saves record the byte length of the content actually read. (#1324)
- Existing incorrect size records need explicit repair. Use Inspect conflicts and file/database differences → Correct recorded file size when the readable current database revision has no conflicts and matches the Vault exactly. The correction retains the file content and timestamps.
P2P synchronisation
- Peer actions and long device names now fit narrow panes. Larger buttons and wrapped labels keep the controls readable and usable.
Improved
P2P synchronisation
-
We can inspect the latest relay, peer, and synchronisation observations in P2P Status. Expand Diagnostic summary below Stats; detailed observations start collapsed.
- Enable Diag to show diagnostic events in the Log Pane without editor-status updates or notifications. Opening the Log Pane also displays its buffered messages.
- Unobserved information is labelled explicitly. An open room does not establish relay acceptance; relay rejection details remain unavailable through the diagnostic summary.
-
We can see sent (↑) and received (↓) database document revision counts in the P2P panes and editor status, and in the main status bar when P2P is our main remote. Counts include Metadata and Chunks, rather than Vault files.
- Directional ⏩ labels show changes-feed comparison progress, including when no revisions need transferring. Each label disappears three seconds after its count last changes; its absence alone does not establish completion. Peers without document statistics retain sequence values labelled
seq.
- Directional ⏩ labels show changes-feed comparison progress, including when no revisions need transferring. Each label disappears three seconds after its count last changes; its absence alone does not establish completion. Peers without document statistics retain sequence values labelled
-
The updated transport incorporates upstream improvements to peer discovery after relay reconnection, missed signalling messages, and stale connections after rejoining or waiting. Connection offers are created on demand.
- All communicating devices in our P2P group, including CLI and WebPeer clients, must be updated together before P2P synchronisation resumes. Trystero 0.26.0 cannot exchange data with the previous transport.
Documentation
- Clarified backend selection and hosting requirements, including Object Storage request costs. Added a guide to P2P diagnostic observations, logs, and transfer progress.