Is it considered acceptable to repost movies or TV shows from Usenet that are not available on any open torrent tracker? Obviously, the reposted content will be left unchanged and will have the exact filename as originally uploaded by the initial uploader.
It is piracy. Do whatever you want. Who cares if someone cares.
You wouldn’t pirate a pirate, would you?
Will I get banned or something because the release is not mine but scene? What about private trackers?
Lol. If you have access to scene releases that aren’t on a private tracker you will probably get an immediate VIP slot.
no
Hmm, so it seems like a shortcut to get a good clout on private trackers.
As another commenter said, please do it.
It’s probably fine, but some usenet trackers/provider explicitly state that you cannot do that. So check if it’s mentioned in the “user agreement”
is lost fedditors a thing?
You can though it’s a bit of a roundabout way of doing it.
P2P releases typically come from private trackers, so you’re having them go from private trackers --> usenet --> public/private torrents
Scene releases that leak to the public typically hit private trackers/usenet around the same time, so you’re having those go scene --> private trackers/usenet --> public/private torrents
In others words anything you’re seeing in usenet has already been uploaded to at least some private trackers & possibly public torrents.
Of course with public torrents anything goes, unfortunately with the demise of RARBG public torrent users are only seeing a fraction of scene/p2p releases. 1337x/TorrentGalaxy does cover some of this but they aren’t covering nearly as much as the RARBG uploaders used to. So IMO if you’re seeing a scene/p2p release that hasn’t already been uploaded at 1337x/TorrentGalaxy then sure go ahead & create the torrent from your usenet download.
deleted by creator
Unclear what you are talking about, you mention Scene but also quote my comment about P2P. Which one did you mean? They are totally different.
The scene doesn’t do anything with torrents/usenet/etc., they are all about their own FTP servers. Yes, other people do have access to them & then spread those releases over to torrents/usenet/etc. but that’s not the scene doing it.
P2P are the internal release groups at private torrent trackers. Most of them are not interested in uploading anything to usenet/IRC. Other people do grab those releases & then spread them elsewhere e.g. usenet/IRC.
deleted by creator
deleted by creator
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.plus the parity files that can be used to recreate missing
.rarfiles if one is missing.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.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!
