3 ms·
I worked on a sync product that had this feature "forever." The problem with the "ignore" feature is that it creates corner cases in almost every use case we ad
by gwbas1c 7y ago
I worked on a sync product that had this feature "forever." The problem with the "ignore" feature is that it creates corner cases in almost every use case we add. A huge amount of engineering resources goes into this feature, even though its only used by a minority of users.
A big problem comes with un-ignoring a file / folder, specifically if someone else has gone and added the same file / folder on another computer or in the web. The only way to make that use case work smoothly is to basically read minds, because there's no way to know which version of the file / folder is the right one.
- yunruse 7y agoSync conflicts are never fun, but from personal experience programs that attempt to auto-resolve them aren’t exactly letting the user in on what’s going on. The best way to make that work in that case would be to explicitly inform the user when unignoring of the conflict and ask which to keep (showing metadata etc). A quick “retain other version” would help if the user was unsure.
- gwbas1c 7y agoAll I can say is: That's easier said than done. Dropbox's implementation has no UI, building such a wizard is probably much more complicated than they anticipated! I've always advocated for wizards like that, but everyone gets enamored with building the next shiny feature. Some days I wonder if I should just quit and make an open source sync product... And if I'd actually make a living doing it!