You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Torznab feeds sometimes contain extended attributes that can be very useful for filtering. For example, "tag" named attribute is sometimes used to indicate 2x upload torrents, for example. Something like
<torznab:attr name="tag" value="doubleupload" />
Other potentially useful attributes include the number of seeders ("seeders" attribute) and leechers ("leecher" attribute) and finished downloads ("grab" attribute) at grab time, e.g., for checking whether you are early in a swarm. Since the availability of these attributes varies from tracker to tracker, it would be nice to have a custom solution that users can tailor for specific trackers in each filter.
Describe the solution you'd like
A new section in a filter that allows users to define the attribute(s) and value(s), preferably with an option for regex matching.
Describe alternatives you've considered
A more user-friendly alternative is to parse only specific attributes, and have a separate filter option for each. However, I prefer the flexibility that my proposal offers. The middle-ground approach is to give a widely available attribute (e.g., seeders) its own section while allowing custom attributes.
The text was updated successfully, but these errors were encountered:
I think having some very advanced option to use xpath or jq can greatly extend the flexibility of the software, so that we can use the tool on more complex scenarios without having to wait for the exact feature to be developed
Is your feature request related to a problem? Please describe.
Torznab feeds sometimes contain extended attributes that can be very useful for filtering. For example, "tag" named attribute is sometimes used to indicate 2x upload torrents, for example. Something like
<torznab:attr name="tag" value="doubleupload" />
Other potentially useful attributes include the number of seeders ("seeders" attribute) and leechers ("leecher" attribute) and finished downloads ("grab" attribute) at grab time, e.g., for checking whether you are early in a swarm. Since the availability of these attributes varies from tracker to tracker, it would be nice to have a custom solution that users can tailor for specific trackers in each filter.
Describe the solution you'd like
A new section in a filter that allows users to define the attribute(s) and value(s), preferably with an option for regex matching.
Describe alternatives you've considered
A more user-friendly alternative is to parse only specific attributes, and have a separate filter option for each. However, I prefer the flexibility that my proposal offers. The middle-ground approach is to give a widely available attribute (e.g., seeders) its own section while allowing custom attributes.
The text was updated successfully, but these errors were encountered: