prowlarr / sonarr / radarr useability #369
Closed
+45
−26
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change enables clicking on found searches in Prowlarr, radarr and sonarr to view bitmagnet permalink details.
It is odd to have used
comments
attribute of torznab message. This was assessed by scanning Prowlarr code for how it handles generic torznab indexers. Also discovered that Prowlarr usesleechers
notpeers
in constructing peers n / m column. Where n is seeders and m is leachers.Also explored using https://wiki.servarr.com/en/prowlarr/cardigann-yml-definition This however results in significant duplication plus fixed list of base URLs. Which really isn't good for a self hosted component where it cannot be pre-determined how someone is hosting and hence a static list of IPs / hostnames