Sync & Conflict Resolution (Advanced)
This page explains how sync behaves at a system level.
Cross-tab communication
- Tabs share updates through a fast local channel
- Updates are batched to avoid flooding
- Echo prevention ensures you don’t see your own changes bounced back
Cloud sync
- Changes are saved to the server as versions
- Other sessions subscribe to updates
- New versions are delivered automatically
Conflict resolution
The system uses a last-write-wins strategy with version ordering:
- Each save includes a version reference
- Older changes are rejected if a newer version already exists
- This prevents silent overwrites
End-to-end timing
Sync is not instant. The typical flow:
- You stop editing
- Changes are saved shortly after
- The server stores the new version
- Other sessions receive the update
Total: a few seconds from edit to sync.
Why this model works
- Prevents data loss
- Avoids merge conflicts
- Keeps all sessions consistent
- Users stay in control of when to apply updates
Back to: Remote Sync
Last updated on