starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

Add an "Already downloading" column in search result #7674

New issue

Open

opened 2026-02-21 19:06:36 -05:00 by deekerman · 8 comments

deekerman commented

2026-02-21 19:06:36 -05:00

Owner

Originally created by @Cqoicebordel on GitHub (Aug 28, 2018).

Everything is said in the title.
I would love a column in the search result signaling torrent already queued.

Originally created by @Cqoicebordel on GitHub (Aug 28, 2018). Everything is said in the title. I would love a column in the search result signaling torrent already queued.

deekerman added the

Feature request

Search engine

labels

2026-02-21 19:06:36 -05:00

deekerman commented

2026-02-21 19:06:41 -05:00

Author

Owner

@glassez commented on GitHub (Aug 28, 2018):

I don't think there's any reliable way to match some particular search result to a torrent without downloading it.

@glassez commented on GitHub (Aug 28, 2018): I don't think there's any reliable way to match some particular search result to a torrent without downloading it.

deekerman commented

2026-02-21 19:06:41 -05:00

Author

Owner

@Cqoicebordel commented on GitHub (Aug 28, 2018):

The hash is present in both sets, I think.

@Cqoicebordel commented on GitHub (Aug 28, 2018): The hash is present in both sets, I think.

deekerman commented

2026-02-21 19:06:41 -05:00

Author

Owner

@glassez commented on GitHub (Aug 28, 2018):

Search result can have any kind of link. The only case when hash can be obtained is direct magnet link (containing hash in it). In other cases we have no reliable torrent id.

@glassez commented on GitHub (Aug 28, 2018): Search result can have any kind of link. The only case when hash can be obtained is direct magnet link (containing hash in it). In other cases we have no reliable torrent id.

deekerman commented

2026-02-21 19:06:41 -05:00

Author

Owner

@Cqoicebordel commented on GitHub (Aug 28, 2018):

Hmm.
In that case, it could be done, depending on the engines. With a status "?" when you don't have access to a magnet link/hash ?

But indeed it's more problematic there.

@Cqoicebordel commented on GitHub (Aug 28, 2018): Hmm. In that case, it could be done, depending on the engines. With a status "?" when you don't have access to a magnet link/hash ? But indeed it's more problematic there.

deekerman commented

2026-02-21 19:06:41 -05:00

Author

Owner

@Cqoicebordel commented on GitHub (Aug 28, 2018):

Also, this column could be populated through what our actions was with each link (added to queue, just downloaded the torrent to see its status, etc.)

@Cqoicebordel commented on GitHub (Aug 28, 2018): Also, this column could be populated through what our actions was with each link (added to queue, just downloaded the torrent to see its status, etc.)

deekerman commented

2026-02-21 19:06:41 -05:00

Author

Owner

@Cqoicebordel commented on GitHub (Aug 29, 2018):

Another possibility would be to add the link the search engine gets as metadata of the torrents in queue.
If you combine that with the hash to identify them, you can cover a lot of cases.

@Cqoicebordel commented on GitHub (Aug 29, 2018): Another possibility would be to add the link the search engine gets as metadata of the torrents in queue. If you combine that with the hash to identify them, you can cover a lot of cases.

deekerman commented

2026-02-21 19:06:41 -05:00

Author

Owner

@ngosang commented on GitHub (Sep 16, 2018):

Related #2511

@ngosang commented on GitHub (Sep 16, 2018): Related #2511

deekerman commented

2026-02-21 19:06:41 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 23, 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 23, 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.)**