Most good clients should start seeding from an existing file if you find the original torrent on the web somewhere. Or even one that just has that same file in it.
This is it. If you know where you downloaded from and can match up the file names, just put the movie in the downloads folder (or point your torrent client at the folder containing the movie when adding the torrent). It’ll do a piece-by-piece check then start seeding.
What you can do if you don’t know the file name is start the torrent and let it get to 1%, or enough to get the initial torrent data, pause the torrent, and you should have a partial file in the download folder.
Rename your file to match the new one in the download folder, and overwrite the new file with your existing one. Tell the torrent client to force a recheck, and it should identify your newly renamed file as the correct file from the torrent. Now you just restart the torrent, and you’re good to go :)
The only thing to watch out for is that some torrent programs rename partially downloaded files to stop you confusing them with completed files. It’s usually done by appending something to the end of the filename though, so it’s easy to spot.
A torrent is broken into pieces, and further into blocks. The torrent file contains hashes of all the pieces that make up the full torrent. The client validates each piece that is downloaded and will re-download from another peer if an invalid piece is encountered. The spec goes in to more depth if you’re interested. https://wiki.theory.org/BitTorrentSpecification
A modified file will not pass the original torrent file hash integrity heck, and trackers will not consider a torrent with a modified hash as “the same”. So the bittorrent protocol is actually quite resilient against an injection attack.
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.
Most good clients should start seeding from an existing file if you find the original torrent on the web somewhere. Or even one that just has that same file in it.
This is it. If you know where you downloaded from and can match up the file names, just put the movie in the downloads folder (or point your torrent client at the folder containing the movie when adding the torrent). It’ll do a piece-by-piece check then start seeding.
What you can do if you don’t know the file name is start the torrent and let it get to 1%, or enough to get the initial torrent data, pause the torrent, and you should have a partial file in the download folder.
Rename your file to match the new one in the download folder, and overwrite the new file with your existing one. Tell the torrent client to force a recheck, and it should identify your newly renamed file as the correct file from the torrent. Now you just restart the torrent, and you’re good to go :)
The only thing to watch out for is that some torrent programs rename partially downloaded files to stop you confusing them with completed files. It’s usually done by appending something to the end of the filename though, so it’s easy to spot.
deleted by creator
A torrent is broken into pieces, and further into blocks. The torrent file contains hashes of all the pieces that make up the full torrent. The client validates each piece that is downloaded and will re-download from another peer if an invalid piece is encountered. The spec goes in to more depth if you’re interested. https://wiki.theory.org/BitTorrentSpecification
Thanks!
A modified file will not pass the original torrent file hash integrity heck, and trackers will not consider a torrent with a modified hash as “the same”. So the bittorrent protocol is actually quite resilient against an injection attack.