Working for me as of 05-14-2016:
Code:
http://tracker1.wasabii.com.tw:6969/announce
http://thetracker.org/announce
http://tracker.mg64.net:6881/announce
udp://tracker.piratepublic.com:1337/announce
udp://p4p.arenabg.ch:1337/announce
udp://9.rarbg.me:2710/announce
udp://9.rarbg.to:2710/announce
udp://tracker.opentrackr.org:1337/announce
udp://glotorrents.pw:6969/announce
udp://tracker.leechers-paradise.org:6969/announce
udp://torrent.gresille.org:80/announce
udp://explodie.org:6969/announce
udp://tracker.coppersurfer.tk:6969/announce
(Jul 28, 2016, 15:36 pm)whitecat2010 Wrote: [ -> ]Therefore I don't accept it when people say that adding trackers is useless.
If you are doing this regularly to download torrents, then chances are pretty good you have a poorly configured client or computer.
Adding random trackers to find peers is still bad advice.
(Jul 28, 2016, 20:44 pm)Moe Wrote: [ -> ] (Jul 28, 2016, 15:36 pm)whitecat2010 Wrote: [ -> ]Therefore I don't accept it when people say that adding trackers is useless.
If you are doing this regularly to download torrents, then chances are pretty good you have a poorly configured client or computer.
Adding random trackers to find peers is still bad advice.
I don't do it regularly, only if something has zero seeds and I have no other option: either this, and the torrent is mine (about 90% of the cases) or I have to forget about it.
(Jul 29, 2016, 13:00 pm)whitecat2010 Wrote: [ -> ] (Jul 28, 2016, 20:44 pm)Moe Wrote: [ -> ] (Jul 28, 2016, 15:36 pm)whitecat2010 Wrote: [ -> ]Therefore I don't accept it when people say that adding trackers is useless.
If you are doing this regularly to download torrents, then chances are pretty good you have a poorly configured client or computer.
Adding random trackers to find peers is still bad advice.
I don't do it regularly, only if something has zero seeds and I have no other option: either this, and the torrent is mine (about 90% of the cases) or I have to forget about it.
Fair enough. There are edge cases where this does work. As long as your end is configured and working properly, then it is likely the one or two peers you are finding that aren't configured properly. In other words - their configuration is preventing them from showing up in DHT and by pure luck they are announcing to one of the trackers in that list, which may or may not have been included in the torrent's original tracker list.
To be clear: when all else fails, there is no harm in trying this. But not as a regular practice or when creating torrents. Doing so is really just wasting your own bandwidth.
Ironically, in the edge cases where this works--torrents with low-single-digit swarms where none of the seeds are announcing to DHT or any of the same trackers as you or any of the peers you are connected to--doing something completely different will work even better.
Trackers come and go continually so single static lists will always be out of date and incomplete. That's the reason these threads roll on and on.
They're also always far larger than necessary because when you're looking for a single seed (and if there are multiple seeds you won't be worrying about this anyway) then you only need one tracker. It just has to be the right tracker.
How do you find the right tracker? The one that is actually live right now and being used by an actual seed right now? Take the hash of the torrent and search for it on torrentz.eu -- it will tell you.
In the meantime, lists like this are being used by people creating torrents, which kills off the trackers quicker (by overloading them with redundant announces) and fragments swarms--slowing downloads and killing of the torrents quicker.
Lists like this are bad ideas all round.
[To those who will then ask, "so why don't you close the thread?" The answer is that another one would just be created by some other misguided but well meaning fool.]