I am new here, so I don't know if this question has been asked before (searched but didn't find similar posts). Is there a way to avoid verifying if I seed an existing file/folder to a new tracker?
And if not, is there a reason why this function is not supported yet? I actually find it is a very neat function for those who share resources at multiple trackers.
Thanks!
How to avoid verifying when seeding existing file?
Re: How to avoid verifying when seeding existing file?
You'd think there would be an easy explanation. Say I just created the .torrent file and now it's time to seed it. Why should I have to verify it again since torrent create already just did it, or in your case it's already seeding. Well, it won't be easy to find a ticket or forum post simply addressing the idea.
viewtopic.php?f=3&t=8737
viewtopic.php?f=3&t=11350
and I can't find a concise trac ticket regarding this as all have been convoluted with other types of recheck and verify subtleties.
The main developers, I know are not open to the idea of skip verify but you'll find an implementation here but not patched for the 2.8x branch. I keep this fork updated to all the bug fixes and lots of added enhancements that users seem to want. Last update a couple of days ago https://github.com/cfpp2p/transmission/ ... /svn/trunk
https://github.com/cfpp2p/transmission/wiki
Use this only when you know exactly what you are doing!
Take this warning seriously.
Since the piece data itself is not checked against the checksums
in the torrent, using this function with partially complete files
will result in bad data being sent to peers. This is not what you want.
Take extra care when using this function, or just don’t use ‘Skip Verify
viewtopic.php?f=3&t=8737
viewtopic.php?f=3&t=11350
and I can't find a concise trac ticket regarding this as all have been convoluted with other types of recheck and verify subtleties.
The main developers, I know are not open to the idea of skip verify but you'll find an implementation here but not patched for the 2.8x branch. I keep this fork updated to all the bug fixes and lots of added enhancements that users seem to want. Last update a couple of days ago https://github.com/cfpp2p/transmission/ ... /svn/trunk
https://github.com/cfpp2p/transmission/wiki
Use this only when you know exactly what you are doing!
Take this warning seriously.
Since the piece data itself is not checked against the checksums
in the torrent, using this function with partially complete files
will result in bad data being sent to peers. This is not what you want.
Take extra care when using this function, or just don’t use ‘Skip Verify
Re: How to avoid verifying when seeding existing file?
Awesome! I will try it out. Thanks for the development and maintenance!
I don't understand why the main developers don't want it, particularly when you have done such extensive work.
I don't understand why the main developers don't want it, particularly when you have done such extensive work.
Re: How to avoid verifying when seeding existing file?
You will need to use the web client from https://github.com/cfpp2p/transmission/tree/masterCNOrca wrote:Awesome! I will try it out. Thanks for the development and maintenance!
I have also patched Transmission Remote GUI for the added features. The source code https://github.com/cfpp2p/transmission/ ... GUI/source compiles with with lazarus-0.9.30 and fpc-2.4.2 Look in the Old releases for your platform http://sourceforge.net/projects/lazarus/files/ For Windows it's already compiled here http://sourceforge.net/projects/transmi ... mon/files/