Should I vibe code
Paid sync service for a local-first Markdown knowledge base
Sync is the hardest problem you will ever underestimate, and the loser is your notes.
?
Their verdict, the Sync price and the build-time estimate come from their entry, MIT-licensed. Checked 2026-08-03.
?
Our verdict, the regret score and everything below it. Editorial and unsponsored — nobody can pay to be moved.
The honest answer
why the verdict is what it is
Copying files between machines looks simple until two edits collide. A homemade sync that silently resolves a conflict the wrong way destroys work you did not know was at risk, and $5 a month is remarkably cheap insurance.
What actually breaks
not "if". the specific failures.
- Two edits to the same note, resolved by picking one and discarding the other
- A partial sync that truncates files
- Clock skew between devices making "latest" meaningless
- A deletion propagating everywhere before you notice it was a mistake
You wrote two thousand words on the train, offline. At home, the desktop had an older copy open. The sync ran, decided the desktop version was authoritative because its mtime was somehow newer, and overwrote the file. There is no version history, because you were going to add that later.
Is that you?
the verdict is a default, not a law
- It is one-way — a backup, not a sync
- Conflicts are preserved as separate files rather than resolved
- There is versioned history you have tested restoring from
- Two devices can edit offline and reconcile later
- Conflict resolution silently picks a winner
- Your notes are not backed up by something other than this
If you build it anyway
the checklist, then the prompt that enforces it
- Never resolve a conflict by discarding. Write both versions with a suffix and let a human decide.
- Use content hashes, not modification times. Clocks lie, especially across devices.
- Append-only history so any state is recoverable.
- Test with the network cut mid-transfer. That is the case that eats files.
- Keep an independent backup that this tool cannot touch.
I want to sync a folder of Markdown notes between devices. Sync is where data goes to die, so: 1. Start with one-way backup, not two-way sync. Get that correct and running for a fortnight before we discuss bidirectional anything. 2. Identify files by content hash, never by modification time. Clocks across devices are not trustworthy and you should say so in the code comments. 3. Conflicts are NEVER resolved automatically. If both sides changed, write both as 'note.md' and 'note (conflict 2026-08-03 from laptop).md' and leave them for me. Do not merge, do not pick a winner. 4. All writes are atomic: temp file, fsync, rename. A transfer interrupted halfway must never leave a truncated note. 5. Deletions do not propagate on the first sync. Stage them, report them, and require confirmation. A deletion loop is the fastest way to lose everything. 6. Keep an append-only history of every version pushed, addressable by hash, with a 'restore to timestamp' command. Write that command before the sync itself. 7. Add a --dry-run that lists every intended create, update, delete and conflict, and default to it. 8. Test plan in the README: kill the process mid-transfer, edit the same file on both sides while offline, and delete a file on one side. Tell me to run all three before trusting it.
That one keeps you out of trouble. For the prompt that actually builds it, canivibecodeit.com has one.
their build prompt ↗Or don’t build it
the boring option, and the way back out
This is the strongest "just pay" case on the whole site. Obsidian Sync is $5 a month, end-to-end encrypted, with version history. Your notes are worth more than sixty dollars a year and sync is genuinely hard.
$5/mo is cheaper than your weekend.
The notes are already plain files, so the exit is to stop running the sync. What matters is that an independent backup exists that this tool has no write access to — so that if the sync is the thing that fails, it cannot take the backup with it.
Open-source continuous file synchronization that can replace much of Obsidian Sync for tec
Questions
Can I not just use Dropbox or iCloud?
You can, and it mostly works, but file-level sync services also resolve conflicts by picking a winner and are known to struggle with many small files edited on multiple devices. Mostly-works is a different guarantee from works.
Why is sync so much harder than it looks?
Because the easy version is a file copy and the real version is distributed consensus with unreliable clocks, partial failures and offline edits. Every sync bug is a data loss bug.
Every week, someone ships something they shouldn’t have.
New verdicts, the worst thing that landed in the trap, and the occasional incident report. No other email, ever.
last reviewed 2026-08-03 · verdict is editorial and unsponsored · shared entry data from canivibecodeit under MIT · not legal advice