-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracker whitelist #996
Comments
That sounds like a weird request. Having more trackers on a torrent generally does not hurt. Have you perhaps found that it impacts performance or usability? |
It definitely wastes some bandwidth and resources by pinging non-working trackers. I'm now thinking that it'd also provide a small privacy benefit by allowing not pinging trackers in the same jurisdiction for ex. |
I think the desired behavior should better be achieved with external tools,
e.g. /etc/hosts and/or firewall settings.
|
Neither of those provides a practical whitelist option. |
I would also be interested in this feature and would be curious on the performance impact if it was possible to only whitelist DHT/PEX/trackerless. Having long lists of trackers isn't that helpful. I guess alternative (for me at least) could be an option to mass-edit trackers, but the only thing I could find on that was a feature request for another Bittorrent client. qbittorrent/qBittorrent#5362 Edit: I found out that while transmission-remote-gtk has no mass tracker editing, transmission-gtk kind of has. |
Technically a script could be written to purify |
My gut feeling is that this is not a feature that many people would use, but I'm not 100% against it. If someone wants to write a PR for it and the code is simple / testable / fast I'd be willing to consider it. Generally esoteric "power user" features like this are kept in the settings.json file instead of being exposed in the GUI. This is partially because Transmission has several native GUIs so adding settings is a lot of work, but equally important is the choice of keeping the GUI experience simple. |
It would be really nice if it were possible to create a whitelist of trackers, rest get not used.
I would personally use it to only use a few specific trackers that work and not make my client bother with the hundreds that don't.
The text was updated successfully, but these errors were encountered: