There are some thoughts/ideas I wanted to share and discuss with the synchting community. Parts of them may have been discussed here and there, but - I think - not in the following context.
I am running a kind of top down hierarchy of syncthing nodes by having one node that is added by all others as introducer (as described earlier here). The problem/thing I’d love to simplify is that there are some nodes syncing a whole directory (the fileservers) and nodes that should only sync parts of that directory (laptops, smartphone, … - let’s call them client-nodes). So right now I have stignore files set up on each client-node. Easier to administer would be a central, per peer-node stignore set up on the introducer-node.
I’ll try to explain that with the following use-case: Sharing a directory, i.e. photos, with somebody else.
In the current setup I have to seperate the folder to be shared from the main share - by putting the directory outside of the main directory or seting up a stignore-pattern to exclude the directory from the main share and setting up a new share.
If there would be a per node stignore for a share, I could just leave everything as it is. I would just add the new node to the introducer, share the main share with that new node and set a stignore-pattern on the share for the new node (on the introducer) that excludes everything except for the photos-directory.
Also it would be nice to maintain the stignores of your syncthing network centralized this way. You just need to open the UI of the introducer to see or adopt the ignore patterns of the connected nodes. Additionally it would be more comfortable to add an android node. Instead of fiddling on the touch screen to type in the ignore patterns you could just sit on a PC, open the UI of the introducer, add the android node and set the stignore-patterns for it.
It could also add some security. Right now I can sync parts of the big, allover share to trusted nodes via stignore on the trusted-node or to untrusted nodes only by separating them from the allover share as described above (what could mean to have to go through UIs of several nodes). If the per-node stignore gets pushed from the introducer to all other nodes, it might not be necessary anymore to seperate a directory from the allover-share in order to share it with an untrusted machine.
I hope you can follow my thoughts. I know, everything quite vague. Maybe something somebody else also thought of? Maybe an inspiration for a new feature?
Thanks for reading.