Conflicts are always going to happen with mobile devices with changing network connectivity.
Can we improve the way they’re handled?
Change the name (and/or date??) of the CONFLICT file so that it’s right next to the file it’s conflicting with, so that we’re more likely to see that there’s a conflict
Run a custom script. Is it possible to run a script so I can backup the 2+ conflicts, and replace them all with a file that shows the changes? Of course, this would only work with text files, but I’m fine with that.
Conflict files appear for a reason: A file has been modified on more than one device more or less at the same time. (Since last sync, anyway.) I argue that for most people in most situations conflicts are a consequence of a problem which should be understood and solved.
My synched password database for example… If I get conflicts that is a consequence of me having edited it in two places without synching in between. I DEFINITELY need to look into that thoroughly: Compare the files and update the password file so that I don’t loose valuable information. (Much like solving any merge conflict when merging conflicting branches in git.)
What you do with your conflict files is totally up to you.
This shouldn’t really be the reason for conflicts. However, I’ve also observed strange conflicts caused by Android devices in the last few months that shouldn’t have taken place at all, simply because nothing has been edited on the Android devices in those folders. I think that there still may some lingering issues that cause conflicts on Android for apparently no reason. I’d like to investigate into them more in the future when I’ve got some time.