New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Parity with Hydra #27
Comments
I'd really like to see the indexer uniqueness rating (number of unique downloads per indexer) and use that data along with the other stats to provide a indexer 'score' per hydra. It's really helpful to weed out indexers that aren't pulling their weight come renewal time. and the bit about showing stats based on catagory would be cool too, say i want to see which are the best indexers for UHD content, etc. |
+1 to |
I believe this doesn't cover the #428 because it's not exactly dynamic filtering. We can set presets as custom filters but we can't filter the resulty instantly for a keyword. Let's say we checked the results and noticed there are multiple uploaders for certain movie release, so we want to filter the results by uploaders name. We have to create custom filter just for this case, we can't filter the results by just typing uploader name. (Jackett filtering model). For this reason, I do not think that the closed request #428 has been fully fulfilled. @the-lazy-fox @bakerboy448 |
Could you add advanced search to filter torrents? Some filters I have in mind are
Greater than, less than, or a combination of both for:
Could you link to this Hydra? I don't know what that is. |
+1 for caching, at least having the option to enable it. It would help with repeated queries due to failures and help keep some of the load off the indexers. |
I would very much like to see at least 'exact string' search support. I'm pretty sure this would have to be an additional filtering step added in the client after the search results are received as different indexers are not as strict on search results. |
Another person here who would love to be able to type to filter results. Saving filters and turning them on and off is clunky. This is the only thing I really miss from Jackett. |
Is caching results planned? its hugely beneficial if you can cache the results for a certain period. |
No. Low benefit given it'd need to be the exact same query |
Why? Is it so unlikely to trigger the same query? One case that comes to my mind would be e.g. you run two Radarr/Sonarr instances, one for HD and 4K stuff, and you manually search for an episode and then you also want to manually search for the same episode on the other instance. Caching that could help reduce waiting time and duplicate/multiple calls to the indexer. |
Most people have different indexer categories setup for their 4k instances, thus the search is not the same and the cache doesn't help in that scenario. |
This would also be beneficial for situations where the first result failed to download. |
I use the same indexer for everything. Only exception would be anime. Even that I use the same indexer but I have another indexer that I prioritize over that one. Edit: |
Not sure what using the same indexer has to do with different categories selected for said indexer in each app? |
* Create option to upload NZB to downloader or to send link for manual downloadsNo plans for an option QUpdate status of downloads from DownloaderNo Plans QPotentially show download queue? Hydra does this, but seems not super importantNo Plans Q1. Create custom categoriesNo Plans Q2. Override search typesNo Plans Q1. TimeoutNo plans to make this an option Q9. Fallback to generated queries if no results foundarr should handle the fallback QAB#62
The text was updated successfully, but these errors were encountered: