Is there any way whenever a new torrent has been added for downloading Qbittorrent to check automatically if the files within haven't been already downloaded in another torrent file?
As long as there is checksum verification that would enable to download simultaneously the files from multiple places at the same time. Especially helpful when the files are not well seeded.
I just want to hear what your thoughts on such a feature.
Different Torrent, but the same files
Re: Different Torrent, but the same files
Typically, a torrent client can't tell whether two files are the same until both have been downloaded.
Re: Different Torrent, but the same files
bob2306 wrote:
> Typically, a torrent client can't tell whether two files are the same until
> both have been downloaded.
That's what I mean. How is the torrent protocol working? Isn't it first announcing the checksum? If not Probably utilizing such a feature in Qt would be quite the novelty.
> Typically, a torrent client can't tell whether two files are the same until
> both have been downloaded.
That's what I mean. How is the torrent protocol working? Isn't it first announcing the checksum? If not Probably utilizing such a feature in Qt would be quite the novelty.
Re: Different Torrent, but the same files
A hash identifies the whole torrent and a hash is used to check the integrity of each individual part. It's only possible to identify a file if it exactly aligns with part boundaries or is padded with dummy files, as it is in BitComet torrent files.
Re: Different Torrent, but the same files
Sooo is it possible?
Re: Different Torrent, but the same files
If the file path and names are 100% match, it will start re-checking the contents and start seeding.
- Mind you, the path must match. If you have a temporary download folder, they will not; you will have to change path each time you add this other torrent.
- Cross-seeding is against most closed site rules, so be careful.
Re: Different Torrent, but the same files
I don't mind cross seeding within private trackers, however can't one have hash check instead of whole file path match?
Cross leeching/seeding within a list of public torrent sites won't be a bad idea.... right?
Cross leeching/seeding within a list of public torrent sites won't be a bad idea.... right?