You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I just noticed the info hashes created by webtorrent-desktop and webtorrent-hybrid are different.
It causes a problem, when I use webtorrent-desktop created a torrent or magnet link and I also want to use servers somewhere else to seed same content to contribute the download seed, but command webtorrent-hybrid seed <the-file> won't work due to the different hash created by desktop software. Any suggestions to make it consistent hash?
The text was updated successfully, but these errors were encountered:
Thanks for reporting this. WebTorrent Desktop uses the result of the "Private" checkbox at torrent creation time to set the torrent's private flag to true or false. Unfortunately, there's an issue with the way this private flag spec was designed. There are actually 3 possible values for the private flag:
private: true
private: false
not specified (defaults to false)
The problem is that private flag is part of the info section in the .torrent file, which means that each of these three values for private will produce a different info hash.
So, what's happening is that webtorrent-cli and webtorrent-hybrid are not setting private at all, while WebTorrent Desktop is setting it to false.
As a temporary workaround until a new version of WebTorrent Desktop is released, you can create a torrent from the command line that matches the WebTorrent Desktop one by explicitly setting private to false like this:
Hi, I just noticed the info hashes created by
webtorrent-desktop
andwebtorrent-hybrid
are different.It causes a problem, when I use
webtorrent-desktop
created a torrent or magnet link and I also want to use servers somewhere else to seed same content to contribute the download seed, but commandwebtorrent-hybrid seed <the-file>
won't work due to the different hash created bydesktop
software. Any suggestions to make it consistent hash?The text was updated successfully, but these errors were encountered: