14 ms·
I suggest including a few of the largest open trackers by default. You'll have a high hit rate for semi-popular torrents, and they can be faster than waiting fo
by JeremyBanks 8y ago
I suggest including a few of the largest open trackers by default. You'll have a high hit rate for semi-popular torrents, and they can be faster than waiting for a cold DHT lookup in most clients. It's a minor decrease in privacy, but the BitTorrent network isn't really eavesdropping-resistant in the first place.
I wish IPFS had finished their BitTorrent support so we could use their standard gateway paths instead. The prefix https://ipfs.io/ipfs/f017b1114 https://ipfs.io/ipfs/f017b1114 should identify a hex-encoded BitTorrent infohash, letting us use a full URL like https://ipfs.io/ipfs/f017b111464d052f755e01d1c947848ad3d22180476a71a94 https://ipfs.io/ipfs/f017b111464d052f755e01d1c947848ad3d2218... through any IPFS gateway, which would resolve the content using a combination of IPFS' own network and BitTorrent with its DHT, but the implementation was never completed.
- sp332 8y agoI haven't used trackers in years. Have you noticed a "cold DHT lookup" taking a long time recently?
- itdaniher 8y agoI don't understand why, but I believe I've observed similar. Possible hypotheses include: DHT Sybil attack? Hash ring bloat? Bad peers distributing exclusively irrelevant content? Wonder if this is a common observation, and if so, what kind of research might elucidate the underlying change.
- tengio 8y agoGood point. Is there any place where to get an updated list of trackers?
- CorralPeltzer 8y agohttps://newtrackon.com/list https://newtrackon.com/list
- DavideNL 8y agohttps://github.com/ngosang/trackerslist/blob/master/trackers_best.txt https://github.com/ngosang/trackerslist/blob/master/trackers...