News for hackers. Stuff that matters.
Re:Open-sourcing F14 for memory-efficient hash tables by ngbronson on Friday April 26, 2019 @07:23PM (#19762634)
I haven't seen those discussions, but is it possible that they were trying to rehash the results of Object.hashCode rather than pass all of the bytes of the original value through a new hash algorithm?

If you haven't seen it before you will appreciate https://accidentallyquadratic.tumblr.com/post/153545455987/r...

Re:Open-sourcing F14 for memory-efficient hash tables by bjourne on Friday April 26, 2019 @08:44PM (#19763005)
Afaik, they augmented the hash function with a random seed, which didn't work out. See: http://emboss.github.io/blog/2012/12/14/breaking-murmur-hash... It appears that SipHash would be enough (for now) to prevent hash poisoning. Most open addressing hash implementations doesn't yet use SipHash though.