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

54500 readers

950 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

Readarr and yENC-Numbersalad (discuss.tchncs.de)

submitted 1 year ago by norgur@discuss.tchncs.de to c/piracy@lemmy.dbzer0.com

8 comments fedilink hide all child comments

Hi there, I've recently tried to use the Usenet and I am amazed how much stuff is on there and at which speeds it can be accessed. Yet... Readarr has been giving me a headache recently and I think this is due to some peculiarity of the Usenet.

It recently started downloading sources to many files with wild naming schemes at the end of the file like

(2019).zip.vol31+32.par2 yEnc

just to complain that it didn't find any files in the download. Now I get that yEnc is some sort of cypher-format and since the files are usually under 10mb, I get that these are probably single chapter or something. Searching the Usenet by hand, I'll usually find many parts of the same audio book with those numbers slapped onto them. Some don't even follow consecutive numbering and contain vol3+79 or something.

So: How am I supposed to download those and how am I supposed to teach Readarr how to handle them?

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

[–] Laser@feddit.de 10 points 1 year ago* (last edited 1 year ago) (1 children)

yEnc isn't a cipher, but rather an encoding for mapping binary to text, similar to base64 (but much more effective). So this denotes yEncc encoding.

The files you're seeing are PAR2 files, which are used for repairing. They're useless without the base file. The file in your example contains 32 recovery blocks. That means if your base file has 32 or less damaged blocks, this parity file can repair it.

Usually, you'd download all files belonging together in a single download and let your downloader do the rest. This is normally done by loading an NZB file that you either get from a Usenet search engine or an indexer.

[–] norgur@discuss.tchncs.de 1 points 1 year ago

Thanks :) Yet... why keeps Readarr fetching those and not the base file I wonder?