mirror of
https://github.com/ngosang/trackerslist.git
synced 2026-04-28 10:55:53 +03:00
[GH-ISSUE #168] Please always include some http trackers in the tracker_best list #149
Labels
No labels
bug
enhancement
help wanted
pull-request
question
waiting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/trackerslist-ngosang#149
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @N46AN on GitHub (Jun 7, 2019).
Original GitHub issue: https://github.com/ngosang/trackerslist/issues/168
A lot of ISPs have strong traffic shaping upon UDP traffic, effectively disabling any contact to UDP tracker as well as DHT. "tracker_best" list is used by a lot of public torrent makers, so not including any http tracker can have negative effect.
For example, recently tracker*.itzmx.com are removed from tracker_best list and this caused users from said ISP not being able to use a lot of recently made public torrents.
@ngosang commented on GitHub (Jun 13, 2019):
Currently there are 2 http trackers in the best trackers list. The scoring algorithm doesn't take in count the protocol. More reliable and more used trackers are first in the list. Some operators running udp and http trackers requested me to put in the list only the udp tracker because it's really expensive for them to have high traffic with the http protocol.
Traffic shaping means slow speed, not blocking connections. Anyway, most of the communications between peers (file transfers) are done using UDP, so you are fucked up anyway...