Hey thank you very much for your effort.
So it seems it cannot know “deleted” therefor produces new. I guess no whay around that other than monitoring locally and respecting what is learned therein (knowledge which is broken anyways if i unsync).
“only 1 client edited, therefore error” makes sense because it would compare against the server-only anyways even if multi users are involved?
I am really relieved there seems to be no predefined winner upon “file exists”.
So remaining question is: does it do this by date/timestamp only or does it size or checksumming too?
I guess this would be for the devs.
I’d be glad to know it wasn’t just timestamps.
But how to handle this danger best-practise?
I had setup a client headless on a samba server, and since such lockups seem to occur from time to time, even (and often) with a complete seaf-cli stop, and there is no history in such a reconstruction, there should be some kind of alert system if it goes wrong. with a team of people just one day of messup can easily jeopardize people’s nerves. I wonder how I should set this up. How/where would we best hook up a mail command for example? … I wonder. …
maybe someone has an opinion what interface is most stable to do this.