feature request: Built-in Jackett addon should not use aggregate indexer

[Damian-11]

Checklist

• I checked that this feature has not been requested before
• I checked that this feature is not in the "Not planned" list
• This feature will benefit the majority of users

Problem Description / Use Case

During my recent setup of AIOStreams with a self-hosted Jackett instance, I spent a tangible amount of time attempting to figure out why Jackett would never return any results before inevitably timing out. This was the case even when the addon's timeout was set to something unreasonably high (e.g. 20 seconds). It turns out that the built-in Jackett addon uses the aggregate indexer, which is incredibly bad practice as a single slow or non-responsive indexer within Jackett will render the entire addon unresponsive (even if there are multiple valid results from other indexers).

Quoting from Jackett's own GitHub page:

A special "all" indexer is available at:
http://127.0.0.1:9117/api/v2.0/indexers/all/results/torznab
It will query all configured indexers and return combined results.

Important Considerations

When to use the "all" indexer:

• Quick setup with fewer configuration steps
• Testing multiple indexers at once

Limitations of the "all" indexer:

• You lose control over indexer-specific settings (categories, search modes, etc.)
• Mixing search modes (IMDB, query, etc.) might cause low-quality results
• Indexer-specific categories (>= 100000) cannot be used
• Slow indexers will slow down overall results
• Total results are limited to 1000

Recommendation: If your client supports multiple feeds, add each indexer directly instead of using the "all" indexer for better control and performance.

Using the aggregate endpoint is undeniably the easiest way to get Jackett to "work", but it's not something which was ever meant to be used outside of testing. As someone not incredibly familiar with AIOStreams, it took me a significant amount of time to realize that the only correct way to use Jackett is to configure a separate Torznab addon for each indexer.

Users have no way of knowing this unless they have prior experience with Jackett/AIOStreams. The built-in Jackett addon seems like the intuitive thing to do for new users -- but by using it they'll fall into the same trap I did.

Proposed Solution

I propose either of two solutions to this issue:

1. Deprecate the Jackett addon. Either add a noticeable warning informing the users that using Torznab is strongly preferred, or, better yet, remove the Jackett addon all together as it is simply a worse way of achieving something that is already possible with Torznab.
2. Rework the Jackett addon to fetch results the proper way. Jackett has an API endpoint which lets you get information about added indexers. This could for example be used to automatically configure a Torznab addon for each indexer with the correct endpoint.

The first can be implemented quickly and requires significantly less work, while the second is more of an ideal long-term solution. Either will work as long as the user is aware that the aggregate indexer is practically usless and should not be used.

To end off, I want to thank you all for the work you put into this amazing addon. Hopefully you'll have the time to address this and make this already great addon even better. Regards.

[webstreamr]

I agree, manually adding indexers one by one directly is a good workaround for now, so this is not a blocker at least.