The hash isn't intended to detect errors, but if you used it for such, then yes.

It's just a raw LZMA2 stream with a preset dictionary and CRC32 checksum.

Thank you for the compliments.

Also, your SIMD stuff is pretty nice.

From the DB export page:

> torpc_sha1_*: hex encoded SHA1 hash of concatenated SHA1 hashes (binary encoded) of the respective block size. For example, the torpc_sha1_16k hash is obtained by breaking the file into 16KB blocks (if the last block is less than 16KB, it is discarded), calculating a 20 byte SHA1 hash for each block, concatenating these hashes, which is then fed through SHA1 to obtain the final hash. The selected block sizes correspond with the most common piece sizes used for torrents, and hence this hash can be useful in trying to detect duplicate torrents which have different info hash values.

This means that errors in the last block will not be detected, right?

> Mediainfo and related data are currently not included mainly due to size and time it takes to dump the data. The data is also compressed using a custom LZMA2 based scheme, which users would need to implement a decompressor for. I may consider including this data if many are interested in such.

This has made me curious about that scheme. Would you mind sharing it or some code implementing it?

Thanks for the awesome site, cute design, and making these database dumps available :) Very cool!