Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upseed finished torrents without initial check #1139
Comments
This comment has been minimized.
This comment has been minimized.
|
after some research i found the way to load the torrent into the client without check the chucks again, its undocumented feature of webtorrent, I found it looking in the webtorrent-desktop client sources:
The "trick" is the fileModtimes variable, its returned by (undocumented) function in torrent objects:
In this way the webtorrent client bypass the checksum of the pieces and load gigabyte files instantly. |
This comment has been minimized.
This comment has been minimized.
|
What value do you assign to fileModtimes? Can I see your code? Can I do this in the browser? |
This comment has been minimized.
This comment has been minimized.
|
@BenmasterTM Yep, you're correct. This feature isn't documented because the API design is quite terrible and I'd like to improve it before too many people start to use it. In the meantime, feel free to use it as this is this same way that WebTorrent Desktop accomplishes seeding upon restart. |
What i want to do is "load" into webtorrent finished torrents like actually client.seed(torrentID) make, but preventing the "check" of the torrent, I mean when you load a previous downloaded torrent in the disk, webtorrent run from 0% to 100% like is checking the file. its possible avoid this in some way? Because if I have many many files completed, if I add with client.seed() cause extreme HDD usage untill finish to check all files.
Im not sure what do this proces, if the proces is spliting chunks in memory or something similar, can be an option to store in disk to load faster and dont make the process again every time the client is started?
Other torrent clients like Deluge dont have this problem, if try to put big quantity of linux ISOS, and let finish, then close and open again the program, the "check" process dont happen, but the files are shared correctly (I see the upload rates of all files changing)