--On fredag den 16 januari 2004 02:22 +0100 Carl-Adam Brengesjö
why lock it to a single hash algorithm? you can't know the hash of the
file you're looking to unless you have downloaded a *.sfv (what
algorithm? is it called sfv, or?) or MD5 (or simlar) file telling it.
The way it is implemented right now is, the client calculates hashes for
the files in your share, and supplies them when sending out search hits.
But of course we can encourage use of a specific hashing algorithm, but I
dont think we should explicitly use one.
I'm pretty sure a lot of the developers (and especially arne) want to
standardize on one specific hashing algorithm, for simplicity's sake.
TTH is what we're using right now, and unless you can supply a good reason
why it's unfeasable, I doubt people will change.
I agree that having a choice is better than not having it in most cases,
but this is not one of those cases. :)
/fnord, who doesn't even code ;)