-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[PolishTracker] Using cookies method (instead of login/password) #8780
Comments
I think it's fine as it is. The cookie method has problems too, it expires each few days and you have to reconfigure Jackett. If this is a huge problem for you talk to the admin/staff of PolishTracker to allow 2 sessions at the same time. |
@ngosang They simply don't (and won't) allow logging in from multiple devices. And the only way to get around that is having the same cookies. They don't expire each few days but each 3 months which is more than enough and shouldn't cause issues. Therefore I would appreciate the cookies method implementation. |
Did you talk to the admins? Explain this issue to them, It's reasonable to allow multiple devices. If they are not interested paste the response and I will do the changes in the code. |
Hey @ngosang. Yes, I did. Because of how their back-end is designed, it's impossible to allow multiple sessions. They advised to use cookies-based method authorization. |
@ngosang Do you plan on switching PolishTracker to the cookie method to allow multiple sessions? |
Jackett 0.16.1523 |
Hi @garfield69 and @ngosang. I would love to let you know that PolishTrackers' API has been updated. It now can be fully used by Jackett. I additionaly asked their staff to make sure it's ready to use. As a user you can get an API key and API is well documented. TL;DR: there are 2 endpoints: Torrents List and Torrent Download. This means there is no longer need for cookie method. API would be the preferred way to go and I hope someone would like to take it and implement API method :) |
PolishTracker doesn't allow multiple sessions, so the only way to get around it would be using the same cookies from the browser (just like it's done with some trackers), otherwise either Jackett or the browser gets logged out. Using the same cookies would solve this issue.
The text was updated successfully, but these errors were encountered: