Thats why I gave up
At least, I never had those problems with DropBox. I’m using a client for all the mentioned OSses. But thats not the point here.
My point/wish is, that syncthing could check “better/harder/with more love” if an existing file could be renamed.
I guess, syncthing always creates a new file on other clients when a local file is renamed, because there is no 1:1 relation for each sync’ed folder.
I just wish, syncthing would check, weather a same file (metadata/indexes?) already exists on a remote folder and therefore just rename it, and not create a new one with a different case, which (we all know) will just irritate the OS and the users
For my technical understanding, it could be something like: make a CRC of the file to be transfered and check with the CRC of the file to be created/overwritten/deleted on the remote system. If the CRC match and the foldernames match and some metadata as well, then syncthing can be 99% sure, its just a renaming. At least, no data will be harmed, because nothing will be deleted. Just renamed. If nothing matches, syncthing then just creates a new file…
Syncthing does versionising, so there must be some kind of “memory” for files…
But hey, I never took a look (ok, just quick one) at the sources…I’m just nagging…
The linux send-only master, you mentioned, will avoid linux users to get updated files/folders from the mac or windows clients. So that’ll not work here. Unless, I do not know or see what you do