TLDR: Is there a way I can just choose files to seed automatically instead of downloading again first?
Pretty new to using torrents and I have a bunch of files I’ve been able to download over time through magnet links. Some of which I was unable to seed for long periods of time so removed but would like to be able to still seed them again.
It doesn’t look like I have torrent files for them and I tried copying the. Torrent file to another folder when using magnets to see if I could get it from that. I was able to get some from that but it seems to just start a Download again. Can anyone explain this process a little bit better for me so I can offer up my files at later times too?
Yes. The hash has to be the same. They have to be identical files down to the last bit. Otherwise when you go to recheck the torrent, it’ll only be a partially completed torrent and you can only seed what you have finished.
Nope, file names can be different. It’s only the contents that are hashed. If there is a difference, the entirety of every affected chunk is unseedable and the chunk needs to be redownloaded (if allowed by the use). Then there’s the infohash that includes filenames but that’s not important.
This entirely depends on your client and the version of libtorrent that it uses. To say with exactitude you would need to know these things. Since we don’t, it’s more accurate to say that it breaks torrent verification.
Additionally, there are renames which can still break verification. Like changing file extensions.
I’m willing to take the risk. It’s like saying “your web browser supports WebGL”. Unless you’re on Opera Mini or something text-based or ancient, we can assume it’s true.
How does changing an extension break verification? It’s just a rename again. I have successfully changed an extension using qBittorrent before and the check passed again. Via its web interface, even!
And no client hashes filenames because they just aren’t what is hashed. I think even TUI ones have internal support for different filenames even if they don’t have a rename function because you can reach limits of your filesystem (path length, character support etc.)
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.
Yes. The hash has to be the same. They have to be identical files down to the last bit. Otherwise when you go to recheck the torrent, it’ll only be a partially completed torrent and you can only seed what you have finished.
Nope, file names can be different. It’s only the contents that are hashed. If there is a difference, the entirety of every affected chunk is unseedable and the chunk needs to be redownloaded (if allowed by the use). Then there’s the infohash that includes filenames but that’s not important.
This entirely depends on your client and the version of libtorrent that it uses. To say with exactitude you would need to know these things. Since we don’t, it’s more accurate to say that it breaks torrent verification.
Additionally, there are renames which can still break verification. Like changing file extensions.
I’m willing to take the risk. It’s like saying “your web browser supports WebGL”. Unless you’re on Opera Mini or something text-based or ancient, we can assume it’s true.
How does changing an extension break verification? It’s just a rename again. I have successfully changed an extension using qBittorrent before and the check passed again. Via its web interface, even!
And no client hashes filenames because they just aren’t what is hashed. I think even TUI ones have internal support for different filenames even if they don’t have a rename function because you can reach limits of your filesystem (path length, character support etc.)