Le 27/04/2026 à 10:56, Nick Rickard via Dng a écrit :
>>>    But! You can configure data retention in Syncthing, so deleted files
>>> get into .Trash-like folder first.  It could be restored.
>>
>>      OK: looks better like this; otherwise it would be pretty dangerous!
>>
>>      This requires a policy: everything you want to keep, you must
>> move to other places; and delete the rest. And this method must be
>> enforced on both sides. I'm thinking of it and it isn't easy to set
>> up this policy, but it would be usefull to have one instead of the
>> current mess (~:
>
> Maybe I could have been clearer. I was trying to emphasise that
> synchronisation means that although your data is in two locations, it
> would be unwise to think that means you have a backup. As Tomasz
> pointed out, Syncthing does have a Trash folder but I personally
> wouldn't use that as an intentional backup. I have never had problems
> with data corruption with Syncthing. I use Syncthing as described for
> my photos and then also have a separate backup policy (copied to a
> remote server, etc) for all my data should it get corrupted,
> accidentally deleted, or subject to fire/flood locally.

    Sure. I understood very well that it is in no way a backup. But,
thinking of it, it raises a question:

    Suppose you remove a file in the Linux directory while the phone is
not connected and then, another day, you connect the phone; there are
two possibilities:

    1) the file is deleted on the phone,

    2) the file is copied again from the phone to Linux.

    How can Syncthing know what to do? Is it keeping track of the
history like git?

--     Didier