Klaus_1250 Posted April 5, 2006 Report Share Posted April 5, 2006 I was recently scouring the web for a different, currently difficult-to-download, torrent. I came across the same torrent, though different piece size, on another tracker. When downloading the torrent in uTorrent, uTorrent acted as if the torrent was already there (since the previous, still active, torrent had the same file name), checked the file, and started downloading. Both torrents now used the same source file, though different trackers and piece sizes and they seemed unaware of eachother.Not sure if the bug is that uTorrent didn't recognize that the file was already "taken", or that the two torrents were unaware of eachother. It should at least issue a warning and give an option to resume / continu the torrent on the other tracker and mark the previous torrent / tracker as temporary disabled. Personally, I would love to see an option for multi-tracker torrent, with different piece sizes. Should be doable, as the complete hash for both files should be the same. Link to comment Share on other sites More sharing options...
Firon Posted April 5, 2006 Report Share Posted April 5, 2006 different piece size = different infohash = NOT THE SAME TORRENT. Link to comment Share on other sites More sharing options...
Klaus_1250 Posted April 5, 2006 Author Report Share Posted April 5, 2006 infohash is different, indeed. Torrent has exactly the same contents though. But, different infohashes, same filename, shouldn't uTorrent give out a warning? Now, i can use the same file for different torrents, but both torrent don't know about each other and doing rechecks every view minutes for both file is too much bother.Also, if someone has added additional hashes, say SHA, MD5, CRC32, tigertree or whatever, wouldn't that be the same for both? (again, different piece size, different infohash, same contents and I presume those other hashes are based on the files contained within the torrent). Link to comment Share on other sites More sharing options...
Ultima Posted April 5, 2006 Report Share Posted April 5, 2006 A lot of times, same filenames mean nothing, and the files themselves might still be different. µTorrent can't verify that each file is identical until each one is present, meaning that in the end, you have to download it, so a warning doesn't help much. Link to comment Share on other sites More sharing options...
Firon Posted April 5, 2006 Report Share Posted April 5, 2006 A different infohash (even if it's -only- the piece size) can mean that the files are completely different. It may not be the case, but µTorrent cannot assume that they are the same. Link to comment Share on other sites More sharing options...
Klaus_1250 Posted April 5, 2006 Author Report Share Posted April 5, 2006 @Ultima: No, but if both would be different, I'd be downloading two different torrents to one sourcefile. That can't be right.@Firon: uTorrent can't assume that, but a force button in such cases would be handy :-) Also, if both files would contain a sha1, md5, tigertree, ed2k or whatever hash, uTorrent would be able to tell if both files are the same. Link to comment Share on other sites More sharing options...
Firon Posted April 6, 2006 Report Share Posted April 6, 2006 They don't contain any such hash, and µTorrent doesn't handle anything except the SHA-1 for the pieces. Link to comment Share on other sites More sharing options...
Klaus_1250 Posted April 6, 2006 Author Report Share Posted April 6, 2006 They can. http://wiki.depthstrike.com/index.php/EAD:Utilities:TorrentBuildPersoanlly, I like that approach of torrent with additional hashes, for the simple reason that this way, content can flow more easily flow back and from other networks (edonkey, gnutella). Link to comment Share on other sites More sharing options...
Firon Posted April 6, 2006 Report Share Posted April 6, 2006 yeah, I know they can, but they rarely do. only Azureus and that torrent maker do it, and it's not always turned on. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.