Promising; kinda feels like a hopefully-better syncthing, albeit I think one-direction?<p>Anyways, some hopefully constructive questions that I don't see in the readme:<p>* Is sync done in cleartext? (Or am I misunderstanding the model and this expects you to handle the network layer yourself with eg. NFS?)<p>* How are conflicts handled?<p>* Actually, in general where does this land on CAP? (There's a section titled "Consistency" but it doesn't really answer what I want to know)<p>> If enable_versioning is active, the daemon creates zero-cost reflink snapshots on fsync:<p>* How does it handle filesystems that doesn't have that feature? (XFS and BTRFS are easy, but this says it supports ext4)<p>(And to be clear, none of these are meant as criticisms of the actual software; they're things that the user should <i>know</i> the answer to, not questions that have to have a specific answer)
It reads to me like encryption is handled one layer below this by NFS. I would naively assume this should be set up with external changes disallowed since it is capturing and replaying fs events.<p>I would love to see a replacement for syncthing though. Something with less config knobs, that 'just works' and handles conflicts more intelligently.