[Read-only sync behavior: feature or bug?]

On 31.1.2016 at 0:42 AM, GreatMarko said:

If you make changes on a RO node, in order to bring that node back in alignment with its "master", you'll need to select the "Overwrite any changed files" option in the RO folder's preferences.

Thanks to your reply I know now that the "bug" I am fighting with for so long is actually intended. :-p

This is quite a problem for me. Is there a similar setting on Android - I couldn't find any.

I'm syncing a folder with my most important notes and stuff to my mobile devices, so I'm always able to access them, but I do not want them to make any changes. I'm using Jota for text file, however if I just type a small change into a file, the synchronization breaks - even if I discard the changes. Unfortunately this happens from time to time by accident. I didn't know for a long time that this was causing my sync issues. So I end up being somewhere and when accessing my notes I realize I'm missing the latest information.

Even worse, I didn't even find a way to easily fix the synchronization again. Turning on selective sync, deleting all files, rebooting device, turning off selective sync again, updating the file on a read/write device, ... - still those files will not get synced any longer. So every time this happens I need to disconnect the whole folder, delete everything and sync it again.

Please tell me there is a simpler way to keep it mirrored. Thanks!

[Insufficient Free Space Warning]

Hi again,

 

what do you think about a warning when a device goes online and the free space is insufficient for the files to be received (set syncing to pause and requiring manual action to resume)? A completely full drive can cause unexpected program behavior and this would make it possible to notice and react before running into errors.

 

 

[Conflict Resolution]

Hi,

 

obviously this is not a never-before-seen topic, however surprisingly I could not find any that isn't already quite old or different/more complicated than my very basic use case.

 

I still use FreeFileSync for some things, because it gives me the opportunity to review what has changed and what will be done. For some kind of data this won't change as it is just a different concept and there is no intention Sync should be the first choice for such use cases.

 

However, basic conflict notification/management would be a big improvement already for most of them. There is no need to unlink/re-link devices, synchronize folders with other existing folders etc.

 

Just knowing that when 2 devices that see each other for the last time at T1, later at T2 device A updates a file and at T3 device B updates the same file before meeting again at T4, the revision of device A will be silently moved to the Archive does not really give me a good feeling using Sync for shared working or critical data.

 

Just a simple notification that there was a conflict (changed file on both sides since last sync.) would defuse this issue a lot. You could react to the problem before it might be too late already when you notice it or when it's still no big mess to fix it.

 

PS:
Tested with 2.2.7 on Windows and 2.2.4 on Android

 

Thanks for reading!