I assume there’s some historical reason for this, but currently, the way scene releases reach most people seems to consist of:
Sites that track releases post the nfo file of the release; these sites generally don’t provide the release itself.
People then look for the release via various channels and download it.
Wouldn’t it make sense for the nfo to contain the checksum of the actual release, letting pirates verify unmodified copies of it and making it easier to avoid versions that have been modified in various ways?
Obviously you’d still have to trust both the site where you got the NFO (and therefore the checksum) and the people who made the original release, but those are usually relatively trustworthy, being known people who have handled a lot of releases with no problems - a lot of the danger of viruses and the like in software piracy comes from the risk of middlemen adding something.
Point 2: “Sites which track NFOs” track NFO files of scene releases because noone cares about P2P NFOs. Scene releases are intended to spread on FTP, not BitTorrent. They also come with CRC-32 checksums in file extension .SFV
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Point 2: “Sites which track NFOs” track NFO files of scene releases because noone cares about P2P NFOs. Scene releases are intended to spread on FTP, not BitTorrent. They also come with CRC-32 checksums in file extension .SFV
my bad. deleted my previous guesses since it seems i missed a few key words there