Previously requested here. I think AICH hash is common by now - right now >80% of ~4000 known clients in my eMule statistics are eMule 44+ clients. It also saved me thousands of Mbs of recovering from corruption (not to mention Gigs of redownloading for corrupt files from non-ED2K sources, with help of mod mentioned in that thread, that is now public). So, isn't it time to add it?
i would like to see TTH too as its the hash used in DC and it could really help finding the right file when a corrupted version of the file is also floating around.
for new hashes to be included into anidb they need to be supported by AoM first.
once AoM can calculate them we can think about including them on AniDB.
PetriW wrote:But AICH? Wasn't that flat out denied previously due to the very long hashes?
No, read that thread again: DB would store only master hash - same hash that passed in ed2k link.
Just for example, it looks like this: ed2k://|file|UsageTrack.txt|16|0238D5C800F1052539B687D1158137CA|h=NHIBJOVBCMTJE4C7B2RC4HKCX7YUQRHK|/
(part after h= is AICH hash)
If you need it I'll try pulling AICH calculation from eMule source this Monday, when I'll be porting my mod to new version.
PetriW wrote:O_o;
I thought it was the other way around.
well,
IMHO additional hash fields are useless if they aren't filled by default.
so in order for them to be usefull AoM would need to support them and I therefore think that it's best to wait untill it is clear whether AoM will support a hash in question or not.
and anidb would of course not store full AICH hash sets but only the master key. and if we include that one or not might still be a topic for some discussion.
same goes for any other hashes.