Repository navigation
[FR] Source Indexer Filter for Cross-Seeding #1373
Replies: 1 comment
Agent BriefCategory: enhancement Current behavior:
Desired behavior: Edge cases and error conditions to settle:
Key interfaces:
Acceptance criteria:
Out of scope:
Why a human: Two product calls come first. The request asks for a Source Indexer filter, but source torrents in qui carry qBittorrent announce URLs, not the identity of a configured Torznab indexer, so a maintainer has to decide whether the filter keys on tracker host, on tracker customizations and friendly names, or on a mapping to configured indexers. A maintainer also has to decide which cross-seed entry points it covers (RSS, webhook, completion, seeded search, Dir Scan) and where the control lands in the settings UI. |
Uh oh!
There was an error while loading. Please reload this page.
As some trackers don’t allow cross-seeding exclusive releases until the exclusivity window has ended.
The optimal solution is to add a “Source Indexer” option for cross-seeds, similar to the existing Target Indexer filter, but used to filter which indexer a cross-seed can originate from, rather than which tracker it’s sent to.
All reactions