starred/qBittorrent

Fork 0

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

Strange torlock behavior #6952

New issue

Closed

opened 2026-02-21 18:42:20 -05:00 by deekerman · 7 comments

deekerman commented

2026-02-21 18:42:20 -05:00

Owner

Originally created by @Pireo on GitHub (Feb 25, 2018).

qBT 4.04 Windows 7 64bit ultimate

Torlock seems to redirect to torlock2.com after any search on the site, and the results tend to be pornographic, the vast majority of torrents have 0 seeds and 0 peers. This applies to qBT plugin too.

@ngosang @evsh @sledgehammer999 @Chocobo1
time to ditch it?
Anyway, please add snowfl and limetorrents as official.

Originally created by @Pireo on GitHub (Feb 25, 2018). qBT 4.04 Windows 7 64bit ultimate Torlock seems to redirect to torlock2.com after any search on the site, and the results tend to be pornographic, the vast majority of torrents have 0 seeds and 0 peers. This applies to qBT plugin too. @ngosang @evsh @sledgehammer999 @Chocobo1 time to ditch it? Anyway, please add snowfl and limetorrents as official.

deekerman closed this issue

2026-02-21 18:42:23 -05:00

deekerman commented

2026-02-21 18:42:26 -05:00

Author

Owner

@Chocobo1 commented on GitHub (Mar 9, 2018):

@Pireo
Thanks for the suggestion, unfortunately we have no maintainers now.
Oh and https://github.com/qbittorrent/search-plugins is a better place for such discussion.

time to ditch it?

If you wish, you can submit a PR to https://github.com/qbittorrent/search-plugins

Anyway, please add snowfl and limetorrents as official.

@Piccirello are you interested to help maintain the search plugins repo?

@Chocobo1 commented on GitHub (Mar 9, 2018): @Pireo Thanks for the suggestion, unfortunately we have no maintainers now. Oh and https://github.com/qbittorrent/search-plugins is a better place for such discussion. >time to ditch it? If you wish, you can submit a PR to https://github.com/qbittorrent/search-plugins >Anyway, please add snowfl and limetorrents as official. @Piccirello are you interested to help maintain the search plugins repo?

deekerman commented

2026-02-21 18:42:27 -05:00

Author

Owner

@Piccirello commented on GitHub (Mar 9, 2018):

@Chocobo1 I don't personally have any interest, though the more I think about it the more I like the idea of integrating with Jackett (#7590). Maintaining search plugins seems like it should be outside the scope of qbittorrent, and Jackett has basically abstracted all of this away for us.

I haven't looked into what an integration would actually involve, and it would be an additional piece of software that users would have to install and run. But I think it will be far easier to maintain in the long term than our own custom search plugins (and we'll pick up support for a whole bunch more trackers in the process).

@Piccirello commented on GitHub (Mar 9, 2018): @Chocobo1 I don't personally have any interest, though the more I think about it the more I like the idea of integrating with Jackett (#7590). Maintaining search plugins seems like it should be outside the scope of qbittorrent, and Jackett has basically abstracted all of this away for us. I haven't looked into what an integration would actually involve, and it would be an additional piece of software that users would have to install and run. But I think it will be far easier to maintain in the long term than our own custom search plugins (and we'll pick up support for a whole bunch more trackers in the process).

deekerman commented

2026-02-21 18:42:27 -05:00

Author

Owner

@Chocobo1 commented on GitHub (Mar 10, 2018):

Maintaining search plugins seems like it should be outside the scope of qbittorrent, and Jackett has basically abstracted all of this away for us.

I like the idea of this, however installing Jackett (and .Net) doesn't seem all that easy compared to installing python (I could be wrong).
Another point is, I still couldn't imagine how Jackett can integrate tightly with qbt.
IIRC, one contributor says that qbt main selling point is the integrated search engine, if opening another program/window is required for performing search, then we lose that advantage.

@Chocobo1 commented on GitHub (Mar 10, 2018): >Maintaining search plugins seems like it should be outside the scope of qbittorrent, and Jackett has basically abstracted all of this away for us. I like the idea of this, however installing Jackett (and .Net) doesn't seem all that easy compared to installing python (I could be wrong). Another point is, I still couldn't imagine how Jackett can integrate tightly with qbt. IIRC, one contributor says that qbt main selling point is the integrated search engine, if opening another program/window is required for performing search, then we lose that advantage.

deekerman commented

2026-02-21 18:42:27 -05:00

Author

Owner

@Piccirello commented on GitHub (Mar 12, 2018):

Another point is, I still couldn't imagine how Jackett can integrate tightly with qbt.
IIRC, one contributor says that qbt main selling point is the integrated search engine, if opening another program/window is required for performing search, then we lose that advantage.

Jackett provides an api that we would integrate with. All searching would still happen within qBittorrent.

@Piccirello commented on GitHub (Mar 12, 2018): > Another point is, I still couldn't imagine how Jackett can integrate tightly with qbt. IIRC, one contributor says that qbt main selling point is the integrated search engine, if opening another program/window is required for performing search, then we lose that advantage. Jackett provides an api that we would integrate with. All searching would still happen within qBittorrent.

deekerman commented

2026-02-21 18:42:27 -05:00

Author

Owner

@Chocobo1 commented on GitHub (Mar 12, 2018):

Jackett provides an api that we would integrate with. All searching would still happen within qBittorrent.

That sounds good!
Now the next problem how should we merge into qbt?
I don't think we should ditch the current search engine right away, but should integrate into it.
We could add a new tab "Search (Jackett)" in the main window... or there any better ideas?

@Chocobo1 commented on GitHub (Mar 12, 2018): >Jackett provides an api that we would integrate with. All searching would still happen within qBittorrent. That sounds good! Now the next problem how should we merge into qbt? I don't think we should ditch the current search engine right away, but should integrate into it. We could add a new tab "Search (Jackett)" in the main window... or there any better ideas?

deekerman commented

2026-02-21 18:42:27 -05:00

Author

Owner

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

@Pireo @sledgehammer999 close this issue.
Official torlock plugin is working fine. And yes, we should support Jackett but there is another issue for that.

@ngosang commented on GitHub (Sep 15, 2018): @Pireo @sledgehammer999 close this issue. Official torlock plugin is working fine. And yes, we should support Jackett but there is another issue for that.

deekerman commented

2026-02-21 18:42:27 -05:00

Author

Owner

@Chocobo1 commented on GitHub (Sep 15, 2018):