Jackett: Freeleech tokens

[rubdos]

Certain trackers (AR et al.) allow for the use of "freeleech tokens" on certain backlog torrents. Many of these trackers offer so many of these tokens that it's almost guaranteed to have them at all times.

It would be nice if one could configure Jackett to return freeleech-token-enabled Torrent urls, or have them configurable in the client software (radarr/sonarr), e.g. a checkbox "use freeleech tokens when available".

E.g. for AR, the difference in Torrent url is "&usetoken=1".

[kaso17]

Having a option to append &usetoken=1 wouldn't be a problem.
Can you please test what happens when you add &usetoken=1 to torrents which don't support FL tokens and what happens if you use &usetoken=1 but have no more tokens available?
If you still get a valid torrent file it would be easy to implement.

[rubdos]

Can you please test what happens when you add &usetoken=1 to torrents which don't support FL tokens and what happens if you use &usetoken=1 but have no more tokens available?
If you still get a valid torrent file it would be easy to implement.

I know I get a valid torrent in both cases. This is for Gazelle based trackers (APL,AR). When you use usetoken=1 on a global freeleech torrent, no tokens are subtracted, and iirc, nothing happens if you run out.

[kaso17]

implemented via 29f111aec40ef9defaf8afd513b8ad4ae3a02c71

[rubdos]

I'm going with a very vague bug statement here: "it doesn't work". I checked the "use freeleech tokens" checkbox. How do I debug this? (Make a new issue?)

[kaso17]

please enable enhanced logged and try downloading a torrent, you should see the download link (including the usetoken part in the log)

[karelvanhecke]

@kaso17 I tried it with AR and it uses usetoken=0 in the URL, even when enabled.

[rubdos]

@kaso17 I tried it with AR and it uses usetoken=0 in the URL, even when enabled.

Ha, thanks for trying this. I didn't have much time to test lately.

[kaso17]

Working fine for me (uses &usetoken=1). Can you please share an enhanced log (-t and -l command line option) while doing the indexer configuration (enable freeleech tokens), a search and then the download?

[karelvanhecke]

@kaso17 I readded AlphaRatio and that fixed the issue. I can now confirm tokens are being used. This issue can be closed.

[rubdos]

Can you please test what happens when you add &usetoken=1 to torrents which don't support FL tokens and what happens if you use &usetoken=1 but have no more tokens available?

Apollo sadly returns

<p>This torrent is too large. Please use the regular DL link.</p>

when requesting freeleech on >2GB. :'(

Shall I open a new issue for this?

[kaso17]

@rubdos do you know if other gazelle trackers return the same error for large torrents or is it just Apollo?

[rubdos]

@rubdos do you know if other gazelle trackers return the same error for large torrents or is it just Apollo?

Afaik it's APL, since they only allow FL tokens to be used on sub-2GB torrents.

[kaso17]

fixed via fc3d8d1aec83315b2d58ade10392949ab3e322d5