why is publicbt the only tracker currently used? wouldn\'t it be best to put in all the open public
trackers to ensure they are almost impossible to take down? or is there some performance problems?
also i have noticed that the torrage .torrent files are on openbittorrent rather than publicbt,
which means they appear to be a completely separate swarm. unless these trackers are cross
communicating with each other, which is possible, although it still leaves the potential for a
takedown or dns block of the only tracker in the list. personally i think it would be a cool project
to setup a tracker that proxies all the other major trackers to see if there is content there. could
be a localhost client end hack even but i guess it might flood things.
i\'ve been adding openbittorrent to the torrents manually but its a bit of a pain.
it would be handy to have:
udp://tracker.publicbt.com:80/announce
http://tracker.publicbt.com:80/announce
udp://tracker.openbittorrent.com:80/announce
http://tracker.openbittorrent.com/announce
http://z6gw6skubmo2pj43.onion:8080/announce
http://z6gw6skubmo2pj43.tor2web.com:8080/announce
udp://tracker.openbittorrent.kg:2710/announce
http://tracker.openbittorrent.kg:2710/announce
http://denis.stalker.h3q.com:6969/announce
there are others too.
personally i think it would be great if torrent index sites added semantic data and some public
api\'s, this would allow for sites to cross scrape .torrent files off each other. there would no
longer be a pirate bay, just anyone who wanted to run a public index could setup a site and scrape
from anyone else, like how the pirate bay index had been scrapped and torrented. this already
happens to some extent with rss but a proper system setup with the intent of distributing the
.torrents into what would basically be one giant database would be great. also some system to handle
spam takedowns.
ps: the "new post button" seems to be missing for me, you can craft the url to make new threads though.
trackers to ensure they are almost impossible to take down? or is there some performance problems?
also i have noticed that the torrage .torrent files are on openbittorrent rather than publicbt,
which means they appear to be a completely separate swarm. unless these trackers are cross
communicating with each other, which is possible, although it still leaves the potential for a
takedown or dns block of the only tracker in the list. personally i think it would be a cool project
to setup a tracker that proxies all the other major trackers to see if there is content there. could
be a localhost client end hack even but i guess it might flood things.
i\'ve been adding openbittorrent to the torrents manually but its a bit of a pain.
it would be handy to have:
udp://tracker.publicbt.com:80/announce
http://tracker.publicbt.com:80/announce
udp://tracker.openbittorrent.com:80/announce
http://tracker.openbittorrent.com/announce
http://z6gw6skubmo2pj43.onion:8080/announce
http://z6gw6skubmo2pj43.tor2web.com:8080/announce
udp://tracker.openbittorrent.kg:2710/announce
http://tracker.openbittorrent.kg:2710/announce
http://denis.stalker.h3q.com:6969/announce
there are others too.
personally i think it would be great if torrent index sites added semantic data and some public
api\'s, this would allow for sites to cross scrape .torrent files off each other. there would no
longer be a pirate bay, just anyone who wanted to run a public index could setup a site and scrape
from anyone else, like how the pirate bay index had been scrapped and torrented. this already
happens to some extent with rss but a proper system setup with the intent of distributing the
.torrents into what would basically be one giant database would be great. also some system to handle
spam takedowns.
ps: the "new post button" seems to be missing for me, you can craft the url to make new threads though.
