3 ms·
> counterclaiming Doesn’t have any s and stemming doesn’t have any possessive. But "oncogene's" (collides with counterclaiming) and "Carib's" (collides with st
by zimpenfish 2y ago
> counterclaiming Doesn’t have any s and stemming doesn’t have any possessive.
But "oncogene's" (collides with counterclaiming) and "Carib's" (collides with stemming) do.
Also I did point out that the 64 and 128 bit variants have no collisions.
- vlovich123 2y agoYeah, but it's an uninteresting test. As others point out, 32-bit XXH3 has the same issue. It wouldn't surprise me if 32-bit AES did too. It has nothing to do with the quality of the hash algorithm & more to do with the fact that you're not building a perfect hash with such a small hash size.
- zimpenfish 2y ago> Yeah, but it's an uninteresting test. On its own, yes, fair, but it was combined with the 64 and 128 bit variants which aren't uninteresting. > As others point out, 32-bit XXH3 has the same issue. Yes, me. > It has nothing to do with the quality of the hash algorithm The original post asked "I would like to see the collision distribution on /usr/share/dict/words." and that is what they got a demonstration of - some collisions on 32 bit, none on 64 or 128 bit. What else could be done to satisfy their original request in a way that would be interesting to you?
- vlovich123 2y agoPoint to the fact that it passes smasher in addition to that 64-bit and 128-bit variants don’t have collisions and ignore 32-bit altogether. I don’t know why libraries even bother producing 32-bit variants at this point because of how easy a collision is.