search

pradt2 / always-online-stun

A list of publicly available STUN servers, refreshed every hour.
MIT License
568 stars 49 forks source link

[Discussion] - Opposing `candidates.txt` for maintainers that don't want their STUN servers tracked like this? #14

Closed zstarvit closed 1 year ago

zstarvit commented 1 year ago

The README contains a section about being able to remove stun servers from parties that don't want their servers listed here - but is there a tracking mechanism to prevent them from being added by someone else in the future again?

Should there be a file similar to candidates.txt that lists out servers that have specifically asked to not be a part of this project? Or is there some other, better, way that you can track which servers should be rejected from new issues/PRs?

pradt2 commented 1 year ago

Hi, thanks for this.

When someone comes and asks for their service to be removed (so far it's happened once), I just comment out the URL in the candidates.txt file. This way the service is excluded from the checks (and it never appears on valid_* lists), and at the same time we remember to never add it again.

If someone complains that their service should be completely removed from this repo, then I will probably tag their issue with a special tag like purge-request, and then for every new service we add in the future, we would first have to look through all previous removal requests, to avoid precisely the scenario you describe. Luckily this hasn't happened yet.

pradt2 commented 1 year ago

If you have ideas on how to approach this better, then let me know, otherwise I'll close the issue