re: “Folder Master” and "Override changes" http://docs.syncthing.net/users/foldermaster.html?highlight=override%20changes
Observation:
The “Override changes” before destroying non-master data offers almost no insight as to where or what the differences about to be lost are. Information about the differences and locations should be offered, so at the very least it is easier to inspect the files if necessary. A direct comparison of all devicenames, pathfilenames, datetimestamps, permissions would be ideal.
Suggestion:
Add button “Inspect difference”: which comparatively displays all of the relevant files and their info.
Offer options to do a one-off “Pull” of specific files from the non-master devices to assimilate them into the master folder. Include manual options for backup versioning.
Is it feasible to implement the following?:
.exclude - already implemented
.include - new feature
.exception - new feature - list of files that can exist in a master folder, but be treated as regular global syncs. (.exception is probably not the ideal word)
Rationale:
Folders like music, ebooks, keys are maintained in a master folder on a central server, but some associated info would benefit from the ability to get selectively assimilated into the master data. eg: playlist edits/creation, temporary bookmark data, modifications to keyfiles. etc. Without the ability to “.include” as well as “.exclude” it can be messy or impossible to allocate a folder as Master, and ALSO other parts of the same folder as desirable to propagate normally.
eg: Theoretically I would have /music as a master folder with .ignore set on all playlists, and then have another non-master share on the same /music folder with .include only specifying playlists. This is messy with multiple syncs - so probably an exemption list for master folders would be easier. Where anything listed in the .exemption would be treated as a non-master sync, and propagated normally - back into the master folder AND synced devices.
eg: I generally do not want my devices to alter my keyfiles, so the master version is kept on a central server and only pushed to the devices. But in some circumstances I DO want to edit the keyfiles on a device, and DO want to be able to determine which device the latest version is on and thereby selectively/manually assimilate it into the master folder.
eg: if i read an ebook on my tablet, and it generates automatic bookmarks or notes, i do want the server’s master folder to be able to accept this data and push it to the other devices. Selectively/manually is good. But through .include AND .exclude logic would also be very useful.
Related yet somewhat different:
