Adding tracker data from all search results with the same hash #15780

New issue

Open

opened 2026-02-22 02:29:20 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-22 02:29:20 -05:00

Owner

Originally created by @drws on GitHub (May 17, 2024).

Suggestion

With multiple search plugins enabled search results often include partially-duplicate (related) results with the same torrent hash. In order to make use of all available information qBittorrent could provide an option to extract and add tracker data from all search results with the same hash (when adding a torrent from search results).

Furthermore the functionality could be improved by also including tracker data from torrent caches such as iTorrents. This is covered by a related feature request #6424, which could be developed together with this one, but they aren't co-dependent.

The proposal here is also partially related to #2511.

Use case

To easily make use of all available tracker data about a single torrent, which is especially helpful when seeder count is low.

Extra info/examples/attachments

No response

Originally created by @drws on GitHub (May 17, 2024). ### Suggestion With multiple search plugins enabled search results often include partially-duplicate (related) results with the same torrent hash. In order to make use of all available information qBittorrent could provide an option to extract and add tracker data from all search results with the same hash (when adding a torrent from search results). Furthermore the functionality could be improved by also including tracker data from torrent caches such as iTorrents. This is covered by a related feature request #6424, which could be developed together with this one, but they aren't co-dependent. The proposal here is also partially related to #2511. ### Use case To easily make use of all available tracker data about a single torrent, which is especially helpful when seeder count is low. ### Extra info/examples/attachments _No response_

deekerman added the

Feature request

Search engine

labels

2026-02-22 02:29:20 -05:00

deekerman commented

2026-02-22 02:29:27 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 25, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)

DO:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 25, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**