Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upUpdate Default Tracker List #957
Closed
Comments
This comment has been minimized.
This comment has been minimized.
|
Do you have a list of suggested trackers to include in The webtorrent project doesn't run a tracker, and leaves that up to the community. |
This comment has been minimized.
This comment has been minimized.
|
I'll have mine up soon. If you are willing to put my tracker in the list that would be great! I would like to track statistics and see if it can handle traffic well. |
This comment has been minimized.
This comment has been minimized.
|
Also, with DHT, trackers are slowly losing relevance. |
This comment has been minimized.
This comment has been minimized.
|
Please send a PR to |
This comment has been minimized.
This comment has been minimized.
|
This thread has been automatically locked because it has not had recent activity. To discuss futher, please open a new issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Ok so I know this is a WT client and all but the two UDP trackers openbittorrent and exodus.desync have been offline and useless for a while. And it's safe to say they probably aren't coming back. So they should be removed from the list of default trackers for sure.
And if webtorrent.io runs the bittorrent-tracker node server then shouldn't we have a UDP and an HTTP for webtorrent that we can add to make it more mainline then what it is? It'd seem more straight if directly affiliated servers are the trackers that are used by default by the client.
Coppersurfer.tk has been having some issues as well and loses connections frequently.