Repository navigation
Disable cross-seed for indexer globally #1331
Replies: 4 comments
|
I do that by disabling the indexer on the settings/indexers page. |
When done like this, the indexer is disabled everywhere, not just for cross-seed. |
|
Currently, on the Auto tab we're able to select target indexers. When we want to run a library scan on the Scan tab, we always have to re-select indexers, and on the Dir Scan tab it's currently not possible to exclude any trackers. To summarize: yeah, I would love to globally select which trackers to include and exclude. In addition, on the Cross-Seed > Auto tab, it would be nice to be able to select the trackers which you want to disable instead of which you want to enable. Currently, when you have one or more trackers disabled and you add a new tracker to your set-up, you have to manually add that new tracker to your target indexers. It's an easy enough action to forget. |
Duplicate of #1275, which asks for the same control from the indexer's own settings page: per-indexer toggles that skip an indexer for cross-seed, per search type or for all of them at once. That thread also covers what the comments here raise. Today the target indexer list lives on the Cross-Seed Auto tab, the Scan tab keeps its selection per run, Dir Scan has no indexer selection at all, and every list is an allow-list, so a newly added indexer is opted in everywhere by default. Putting the switch on the indexer itself replaces all of that with one place. Note that #1373 asks for a different thing: filtering by the indexer a cross-seed originates from, not the one it is sent to. Follow #1275 for this request. |
Uh oh!
There was an error while loading. Please reload this page.
There are many locations where indexers can be selected for cross-seeding. It would be great if cross-seeding could be completely disabled for a specific indexer.
All reactions