Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

54566 readers

505 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others

Loot, Pillage, & Plunder

📜 c/Piracy Wiki (Community Edition):

💰 Please help cover server costs.


Ko-fi	Liberapay

founded 1 year ago

MODERATORS

db0@lemmy.dbzer0.com

sunbrothersco@lemmy.dbzer0.com

dataprolet@lemmy.dbzer0.com

Flatworm7591@lemmy.dbzer0.com

RandomLegend@lemmy.dbzer0.com

Help getting Whisparr to work with private tracker (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by ZeroCooler@lemmy.world to c/piracy@lemmy.dbzer0.com

11 comments fedilink hide all child comments

Ahoy!

I'm a veteran pirate and pretty familiar with the standard *arr stack of resources, but recently decided to run Whisparr.

I also signed up for a new private tracker and got it setup through Jackett and confirmed working in jackett. The problem is, when I manually search for a release in Whisparr it comes back with no results, but searching the same release from jackett (or the tracker directly) I see the release is available.

I think I might know what's going on. I think the tracker has releases dated day/mo/yr and Whisparr is looking for mo/day/yr. This is totally a guess, but it's all I've found so far that might be causing the issue. Was wonder if anyone had a similar issue or a potential resolution.

Thanks in advance!

EDIT: So, I think the issue is the date. Looking at the logs Whisparr searches for "release+yr.mo.d" and the tracker has releases listed with "release+d.mo.yr". I confirmed this by trying the search Whisparr was running manually through Jackett. I guess I'll have to see if I can add additional search terms or something or find a different tracker. I'll update with a solution if I find one

you are viewing a single comment's thread
view the rest of the comments

[–] brickfrog@lemmy.dbzer0.com 2 points 1 year ago (1 children)

If it's indeed an issue then you may want to submit it in their Github so that it could be fixed in the future?

https://github.com/Whisparr/Whisparr/issues

Interestingly someone did submit something similar a while back, but for some reason the submitter closed their own issue without any code being submitted to resolve it. Unclear what happened there or if it's related to your issue https://github.com/Whisparr/Whisparr/issues/58

[–] ZeroCooler@lemmy.world 1 points 1 year ago

I don't know if I'd consider this a issue with Whisparr or with the tracker. All the trackers I've used in the past use UTC standards on date format for releases. I think this new trackers standard is just different for some reason and that breaks Whisparr. Maybe I could put in a feature request to allow the date format to be changed in the query.