search

qbittorrent / qBittorrent

qBittorrent BitTorrent client
https://www.qbittorrent.org
Other
26.35k stars 3.85k forks source link

Swarm Merging #9416

Open zero77 opened 5 years ago

zero77 commented 5 years ago

Can you please implement Swarm Merging like Vuze has.

Because, implementing this can help to find new pears and revive older torrents with few seeders. Thanks

https://wiki.vuze.com/w/Swarm_Merging

zeule commented 5 years ago

This probably should be requested from libtorrent.

calm3285 commented 4 years ago

I just want to say that this is a life changing feature And dont use Vuze souce, use the BiglyBT one https://github.com/BiglySoftware/BiglyBT

allanlaal commented 3 years ago

https://github.com/arvidn/libtorrent/issues/829

https://github.com/arvidn/libtorrent/issues/4936

allanlaal commented 3 years ago

use case:

I read alot. like alot! I use LazyLibrarian to constantly search for and download ebooks/abooks from my Goodreads' "To Read" list with Jackett from a massive list of public trackers. LazyLibrarian then queues them in a torrent client (currently qbittorrent) I'd like the torrent client (qbittorrent) to be able to swarm merge those torrents as usually trackers might duplicate a torrent by adding their own "tracked by xxx" text files & other trash. in addition most (like 80%) of book torrents have little to no seeds or if they are seeded, they are slooooooow af, so thats an obvious use case for swarm merge

Knocks commented 3 years ago

Now that libtorrent-2.0 is out with file-specific Merkle trees, we can start brainstorming possible implementations of this feature. It has to be different from BiglyBT/Vuze because those clients use more complicated and less efficient hash matching, which is no longer needed.

Do the alpha/nightly builds of qBittorent run on libtorrent-2.0?

FranciscoPombal commented 3 years ago

Now that libtorrent-2.0 is out with file-specific Merkle trees, we can start brainstorming possible implementations of this feature. It has to be different from BiglyBT/Vuze because those clients use more complicated and less efficient hash matching, which is no longer needed.

BiglyBT/Vuze have swarm merging for BitTorrent V1, which is still valuable, even if it can never be as efficient as an implementation for V2 due to inherent limitations of V1. Ideally, you'd have swarm merging for both V1 and V2.

Do the alpha/nightly builds of qBittorent run on libtorrent-2.0?

Not currently, no. Support for building with libtorrent-2.0 is slowly coming in.

This is more of a request for libtorrent though: https://github.com/arvidn/libtorrent/issues/4936

Goldmaster commented 3 years ago

I hope this does get added, was about to request the same thing

Bigly has the same thing here https://github.com/BiglySoftware/BiglyBT/wiki/Swarm-Merging

Wonder if the swarm merging could be forked into qbittorrent?