this post was submitted on 14 Aug 2023
40 points (95.5% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54500 readers
848 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Some indexers have a rule that clearly states users that reupload their NZB files elsewhere will be banned, so idk
Does that mean just the .nzb or the .mp4s too? I've been wondering.
In this case, the indexer is talking about the
.nzb, which does usually contain an identifier about which account accessed it. Remember that an.nzbis just a plaintext file providing links to the many split.rarfiles that will be combined during unpacking, plus the parity files that can be used to recreate missing.rarfiles if one is missing.Indexers want to prevent the
.nzbfrom being leaked onto the open internet, or to other indexers, to prevent those links from getting a DMCA/NTD takedown request for as long as possible.There is no way to identify who downloaded a
.mp4, they are not fingerprinted & every person who downloads is getting an identical copy. Share them widely.OH is that what those strange files are?! I need to figure out how to use those! So if something is missing blocks or like only half the movie works I can recreate it out of the other files?
And ok, I figured that was the case, it seemed from the language used on the indexer that I could totally do exactly what the OP wanted as long as I removed the .nzb (and I guess the other files I forgot about) but I figured the actual "content" wasn't even a part of that rule (and of course they could never enforce it, unless they could correlate those uploads with your downloads.)
Here's a quick guide on understanding
.par2files and how to use them. If you're using SABnzbd or NZBget, it should handle these automatically to "repair" the downloaded file, AFAIK.Understanding PAR2 Files - HARLEY HAHN'S USENET CENTER
Oh my mistake, thought you meant these random .srr and .sfv files I keep finding, just went back and checked the extension. Well good info anyway, thanks! But yeah I guess sabnzbd takes care of that then.
Now if I could only figure out how to build Sonarr from source I'd be set, but ./confgure returns a message proclaiming it doesn't exist, and I am in the untarred directory. I'll have to get on their IRC or something I guess. Stack overflow insists autoconfigure (which my system also thinks isn't real) and "just cd into the directory bro" are the only answers, yet still no Sonarr.
.sfv is a text file that lists the crc32's (hash) of the scene release rar files to verify if they are broken/modified in any way. They can sometimes have ascii art in them, or vague info on what topsite the release last went through, but thats rather rare these days. .srr files are created by a program called PyReScene which records exactly how a scene release is rar'd, and with what winrar version to re-create the original release format (rar'd) at a later date. Super useful program for reseeding and cross seeding stuff.
Cool, thanks! Good to know!
Oh, and if you start out with the unpacked files, but don't have a srr file to re-scene them, you can probably find one by searching the release name on srrdb.com. Mileage may vary though.
Cool thanks I'll bookmark it!