Add an option to disable mutual introducer warnings
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
Research direction
Start by locating where Syncthing detects mutual introducers and emits the warning, then trace how configuration options are defined and tested. Add a narrowly scoped option that suppresses this warning, and verify that the warning remains enabled by default and can be disabled through the supported configuration path.
Written by the indexing model from the issue text.
Description
Feature description
A flag or config option to disable mutual introducer warnings.
Problem or use case
I've been running a cluster with multiple mutual introducers without problems for over ten years, since before the warning existed. I know this means I have to delete devices and folders by editing the config file, and have been doing that all this time, too. Having multiple mutual introducers lets me have a few different machines that can introduce new devices to the whole network, and I want to continue with this setup.
So the warnings are just annoying in this case, and it would be great to be able to turn them off, even if it's with an 'I know what I'm doing'-style flag.
Alternatives or workarounds
Just put up with the warnings. Since switching from syncthing-gtk to syncthingtray as a frontend, this has become less feasible, since syncthingtray sends an OS-level notification every time it gets the warning, whereas syncthing-gtk didn't (there I would only see them on the webpage).
- Dominant language
- Go
- Stars
- 89.7k
- Forks
- 5.5k
- Avg merge
- 6h 27m
- Merged PRs (30d)
- 12
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from syncthing/syncthing
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
syncthing/syncthing#10920 · 1 comment ·
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 4/5 3-5 days Newbie friendliness 45/100
syncthing/syncthing#10933 · 3 comments ·
Maintainers usually reply within 1 day
-
enhancement needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 57/100
syncthing/syncthing#10927 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
Maintainers usually reply within 1 day
All issues in syncthing/syncthing
Similar issues
-
fix(handlers): explicitly set Content-Type header in static Index handlerPossibly taken @kage-zero claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Quick Open: restore dependency-directory exclusions in filesystem fallbackPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
eugenioenko/ttt#1206 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-policy-agent/opa#9426 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rorkai/App-Store-Connect-CLI#3192 ·
Maintainers usually reply within 1 day
-
t:urlDecodeUni does not map U+3002 and U+FF61 to a dot, unlike ModSecurityPossibly taken @fzipi claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day