C has new picture: picture pushed to B (not to A)ĭeleting pictures –applies also to modification-:Ĥ) A deletes pictures: nothing else happensĥ) B deletes pictures: deletion propagated to C (not to A)Ħ) C deletes pictures: deletion propagated to B (not to A).B has new picture: picture pushed to C (not to A).A has new picture: picture pushed to B, then 2) happens.

I use Dropbox for backing-up camera pictures from my Android, but I am planing to migrate to Syncthing/Pulse for this and more… stignore, I would still receive updates for those files from other peers but anything I did locally would be ignored.) Previously, if I ignored everything in my. (Interestingly, something like this was possible before we fixed the. Actually figuring out who is in sync with what in such a setup could be something of a nightmare though.

I could see this being solved by having on and off switches for all of creates, changes, deletes, and metadata changes, for both incoming and outgoing directions, per peer node. You're talking about a sync-some-changes-but-not-others where B ignores deletes from A, but maybe allows updates to files and maybe renames, combined with some one way sync so that changes directly on B is ignored. A one way sync here would be B deletes or changes the file and A doesn't care.

Syncthing receive only