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
{{ message }}
This repository was archived by the owner on May 29, 2022. It is now read-only.
I was reading the working modes on the main readme and realized that there is a particular use case that would be very useful in being added. Some trackers, for some reason, have slightly altered root folder and/or filenames, but will otherwise hash check as an exact match.
The strings are only a few characters off, for example tracker A's torrent will download as 'hello.there.2005.1080p.WEB-DL.x264.AAC-BoldOne.mkv' and tracker B's will download as 'hello.there.2005.1080p.WEBDL.x264.AAC-BoldOne.mkv'
The dash is missing from WEB-DL in tracker B's download. I understand the hash_size working mode could be used against this, but seeing as these strings only have a small hamming distance of differences, it could be worked into the Normal mode in order to avoid hash checking the files.
I was reading the working modes on the main readme and realized that there is a particular use case that would be very useful in being added. Some trackers, for some reason, have slightly altered root folder and/or filenames, but will otherwise hash check as an exact match.
The strings are only a few characters off, for example tracker A's torrent will download as 'hello.there.2005.1080p.WEB-DL.x264.AAC-BoldOne.mkv' and tracker B's will download as 'hello.there.2005.1080p.WEBDL.x264.AAC-BoldOne.mkv'
The dash is missing from
WEB-DLin tracker B's download. I understand the hash_size working mode could be used against this, but seeing as these strings only have a small hamming distance of differences, it could be worked into the Normal mode in order to avoid hash checking the files.Thank you for reading.