Meyer is a hotfix. There's one real change: sync was, under specific concurrent-edit conditions, stomping notes. We caught it within 36 hours of reports, fixed it, patched everyone on the stable channel, and wrote this post-mortem.
If you're on 1.0.1 and read nothing else: update now. There's no data loss for anyone still on 1.0.1, but the window is closed the second you upgrade, and the fix is important.
What happened
1.0.1 shipped a sync optimization that cached remote state for 90 seconds to reduce round-trips. The optimization was correct when a vault had a single writer. It was not correct when the same vault was edited concurrently on two devices within that 90-second window.
The failure mode: Device A wrote a change, Device B (operating on cached state) didn't see it, merged from stale base, and on the next sync produced a conflict that resolved in B's favor instead of producing a real merge conflict. The content lost was recoverable from git history (every vault auto-commits on save), but users had to know to look.
Affected: any user with 1.0.1 and two or more devices syncing the same vault who edited the same note on two devices within ~2 minutes.
Scope: we've confirmed 41 vaults affected via anonymous sync telemetry; 14 of those had user-facing note-content regressions. We're reaching out privately to each.
The fix
Two things:
- The cache window is gone. We revert to 1.0.0 behavior — check-on-every-save, which costs ~40 ms per write. We'll reintroduce an optimization, but only after we've added proper conflict detection, which is on deck for 1.0.4.
- Conflict detection is stricter. Any sync operation now checks the full vector clock, not just the head hash. This is what we should have done the first time.
Recovering lost edits
If you think you lost work between Feb 4–6: open the affected note, click the ••• menu → History. Every save is in your local git repo. The blame/diff shows when the stomp happened; you can copy the pre-stomp content back. Clem can also do this for you — @clem recover <note> from before Feb 6.
If you sync to Froots Cloud: we also keep a 30-day encrypted backup of every sync snapshot. Email support@ with your vault ID and we'll ship you the delta file.
Apology
This shouldn't have shipped. Our concurrent-edit test suite covered two-writer cases but not the specific two-writer-within-cache-window case. We've added the missing fixtures, and we're paying every affected vault a year of Pro as a thank-you for the patience.
1.0.3 "Clementine" is on track for Feb 22; the IDE and friends.
— Priya