Repository navigation
[FR] Support for cross-seed to add torrents to different client based on tracker #958
Replies: 4 comments 2 replies
|
For my user case, the best would be to assign a tracker to a single or multiple instances. For example if you have an instance using a VPN you would like to direct specific tracker's results to this instance. |
|
As a simpler request Allow sourcing from multiple qbits but injecting crossseed torrents to a specific qbit. Per instance control rather then per tracker. |
Agent BriefCategory: enhancement Current behavior: Desired behavior:
A routed injection still has to reach the source data from the target instance. When the target instance cannot reach the save path of the matched data, the apply reports a failure status naming that reason and adds nothing. A tracker with no rule keeps the current behavior and injects into the source instance. Key interfaces:
Acceptance criteria:
Out of scope:
Why a human: Feature scope is a maintainer call. The thread proposes two different designs (a tracker-to-instance map versus one fixed injection instance), and routed injection only works when the target instance can reach the same data on disk, so how far qui should go here is a product decision. |
|
I, too, would find this useful. I use one instance for public, and one instance for private, and I'd like my public torrents to be checked by cross-seed and, if found on the private trackers, be added to the private instance. |
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem? Please describe.
I use a different client per tracker. I do this for organization, client whitelist differences, and due to the number of torrents I manage. I would like to use cross-seed, but how I understand that it works is that if I search Client A for cross-seeds, all cross-seed matches will be added to that same client.
Describe the solution you'd like
What I would like is to choose a client to search (or better, search all), and for any matches found be able to specify which client that torrent is added to. For example, if I search Client A and it finds a torrent on Tracker B -- it will add the torrent to Client B.
I don't know the best way to do this. Perhaps tag a client in qui with a tracker, or some sort of custom conditional settings.
Describe alternatives you've considered
As an alternative, I've considered writing a script for qbittorrent to run on-add that will add the torrent to the correct client. Someone pointed out to me that if I do this, cross-seed will attempt to download it again the next run, so I would need to keep the torrent in the client as a place-holder to avoid that.
Additional context
I also use Caddy to proxy announces (session reuse, huge bandwidth savings) which means my current on-add script rewrites the tracker URL to my Caddy URLs. If a torrent's announce URL is used by cross-seed, this may cause further issues on my setup -- unless I could assign a client / tracker URL with a specific tracker.
All reactions