I found this to be quite an annoyance as well. The workaround would be to just have one introducer (per cluster)…
I keep it off now, and whenever I add a new device, I turn it on (on every device) just as long as it needs.
I found this to be quite an annoyance as well. The workaround would be to just have one introducer (per cluster)…
I keep it off now, and whenever I add a new device, I turn it on (on every device) just as long as it needs.
Used this since last year, it was a must with a 15+ cluster. Shame it didn’t remove nodes from other devices as well.
Are there any instructions for use?
Just enable the flag on a device node.
Use it on almost all my nodes.
Only a few machines are within my daily reach, having the others set to ‘introducer’ saves time & travel.
I don’t use it because I couldn’t find any good documentation on what it does
Ofcourse its usefull if you have multiple computers like me.
We should fix that.
Yep. Instructions for use.
It seemed useful at first but I had to turn it off to delete a share that kept being re-added before I could delete it across all devices
+1 for the documentation request.
In a specific use case, we are exchanging business documents with 3rd parties under a Non-Disclosure Agreement. Without fully understanding how introducer works, I won’t use it at all - to avoid the Law of Unintended Consequences … (such as mistakenly leaking a secret).
Yes, absolutely! Introducer is my home server, all other devices just connects to the introducer and done. Would be very painful otherwise, for more than couple devices.
Another thing is when I started sharing some folders with friends (I have couple “myName-hisName” folders), I also just connect to their “server” set it as introducer and our shared folder is on all devices as well. Only downside is that there is now so many devices that I get lost in it and would probably not recognize an attacker… (Lets say there is 5 friends and they each have 5 devices, that is 25 devices + mines)
There was a description once here:
But it seems as if the pictures are not working any more due to the discourse.syncthing.net to forum.syncthing.net change.
Yes! It’s a really handy feature. With caveats.
At the beginning I used it in most nodes for most neighbours and ended up in a strange situation: when two linked nodes (say A and B) are mutually marked as introducer and you want to remove from your cluster a third node C, you end up with C showing up every time you delete it in A or B.
Workarounds:
Yes! Supper useful one for me.
I wish it could come with the option to deprecate nodes when deleted on an introducer as well.
Why is this a poll?
Hope you guys are not planing to drop support. I love it.
Basically I was wondering if anyone actually used it, as I myself don’t and considered it somewhat of a kludge. I’m delighted to see all the answers, and surprised that it is as widely used as it is. This gives guidance that we should probably give some priority to sorting out the remaining kinks - i.e. docs, the flow for actually removing a device, and so on.
If the poll had been 95% “tried it, didn’t like it” I might have considered scrapping it.
This is definitely not something I want to do, but it’s interesting. What if your friend adds their friend as an introducer? I assume those 3rd party nodes get propagated back to you. I guess that you really have to trust your friend.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.