[req]: [speedtorrentreloaded] - add support for downloadvolumefactor and uploadvolumefactor

[sparafucile]

Is there already a request for your feature?

• I have checked older issues, open and closed

Is your feature request related to a problem? Please describe.

The Jackett torznab feed for tracker Speed-Torrent Reloaded sets downloadvolumefactor and uploadvolumefactor to fix values of '1' at the moment (https://github.com/Jackett/Jackett/blob/master/src/Jackett.Common/Definitions/speedtorrentreloaded.yml)

Describe the solution you'd like

The information about the actual volume factors are available on the torrent detail page. Will there be a solution to parse this information and integrate the real values in the Jacket torznab feed?

Describe alternatives you've considered

No response

[garfield69]

The information about the actual volume factors are available on the torrent detail page. Will there be a solution to parse this information and integrate the real values in the Jacket torznab feed?

No there will not. The reason is that in order to provide the DLVF and ULVF states to the torrent list fetched from the search results page, it would necessitate up to 100 additional http GET requests to the web site in order to fetch all the detail pages for every torrent in the search results page.
No WEB site is going to appreciate the increased load on their network if an app is going to perform 101 http GET requests per user every time a search is performed, especially in conjunction with torznab apps like Radarr or Sonarr which automate regular scheduled search query requests.
Its a good way to get your IP flagged as a potential DDoS generator and get suspended or blocked.
Even if were to add a request delay of a couple of seconds to each GET, you run into the issue of reaching the response time limits after which *arr apps will presume the indexer is timed out and flagging it as out of order.