“If it’s a lot of files, that’s going to happen”
I’m coming with some idea of implementation / correction - because with some DSL bandwidth access (upload : 100KB/s), it makes some move impossible to do without using a portable computer with Syncthing, or an USB HDD, and to manually move the big files into the other destination using car and/or public transports (or letting it synchronize back several days or weeks) (for a file that already was on the remote computer, but just moved and get deleted ! That’s so avoidable !) - sometimes I go find some 4G network with my car and laptop to gain some time and fuel (4G : big upload bandwidth) but it’s too bad to have this kind of mission in order to re-upload something that already was on the other side
If I had to code something that would do differently, it would simply be (on the uploader side)
“wait for the analysis to be terminated before committing any change"
"after a file is deleted, re-scan the folder in order to check if it doesn’t appeared somewhere else before committing the deletion” (it can handle the case when the file moved during a folder scan).
The message then contains “file moved” and the remote computer doesn’t delete it.
If it’s not that way it works (no “move” message), “file created” could be sent before “file deleted”. Any way, when a new pair connect after some while, “creation” messages should go before “deletion” messages.
At the end of this operation, no moved file can be accidentally deleted and entirely re-uploaded !
Such improvement on the main function of the project would be very appreciated, by me at least, but may be not only - It’s something that is really missing and very problematic with most of the Home DSL internet connections with low upload bandwidth