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.

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.

  • bad1080@piefed.social
    link
    fedilink
    English
    arrow-up
    10
    ·
    1 day ago

    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.mlOP
      link
      fedilink
      arrow-up
      23
      ·
      1 day ago

      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.