4 ms·

Regarding Sync should be Silent, In a perfect world it would be so, but this is far from it. There is no way to automate this conflict resolution for binary fi

Regarding Sync should be Silent, In a perfect world it would be so, but this is far from it. There is no way to automate this conflict resolution for binary files (if the same file is modified in two places). You can simply pick the latest modified version, but this is less than optimal (the other modifications will be lost then). Even dropbox isn't totally silent, in a conflict such as this, their server keeps revisions (so you can pick and choose the correct one, making it not silent). Silent Sync (in a automated no-user-interaction way) has , is, and always be a dream (at least for the foreseeable future).

sachinag 17y ago
But this is exactly where Dropbox is genius. They just keep both files - they don't scream at you that there's a conflict. In the case that you open up a file and it's not quite right, you're going to look into it. You'll find the alternate file and then copy/paste your changes in. Then you'll re-save and ta-da, you're OK. But there are going to be all sorts of situations where you'll have minor conflicts, and the user will never, ever notice.
- jgmorard 17y ago
  SugarSync also does just that: the file is duplicated and the user is left to resolve the conflict at a later time. Actually it does that in a really clever way so that if users keep editing over the already conflicting versions, it doesn't create new conflict versions but rather treats the new files as further versions of existing conflict duplicates...