Today Synchi is finally public! It's designed for syncing files between two locations (local or over SSH). It detects conflicts, and lets you decide what to do.

Why not rsync/Unison/Syncthing?

rsync has no memory between runs and is one-way
Unison needs to be installed on both sides
Syncthing requires always-on daemons

Synchi runs on demand, works over SSH, and only transfers what actually changed.

GitHub: https://github.com/jakobkreft/synchi
Docs: https://jakobkreft.github.io/synchi/

I use it daily for syncing a shared folder between my machines and an android phone. Works great in combination with Tailscale/WireGuard so that you can sync files remotely.

you are viewing a single comment's thread
view the rest of the comments

[–] bad1080@piefed.social 10 points 4 days ago (1 children)

but conflicts still halt for user input

i never understood this behavior. starting a large data transfer only to come back an hour later to find it halted at 5% due to some conflict. why not put those files at the end of the queue and resume with the rest?

[–] jak0b@lemmy.ml 25 points 4 days ago (1 children)

It doesn't work that way. Conflicts are resolved before any transfer starts. The flow is:

Scan both sides and compare (compute file hashes or just compare mtime, no data transferred)

Show conflicts if any → you resolve them

Show copy/delete summary → you approve

Only then does the actual transfer begin. So you never come back to find it halted mid-transfer. All decisions happen upfront while it's just reading metadata, which is fast even for large trees.

[–] davidgro@lemmy.world 9 points 3 days ago

This makes so much more sense than the Windows behavior.