News for hackers. Stuff that matters.
Re:There are only four billion floats, so test them all (2014) by jcims on Sunday October 11, 2020 @01:31PM (#24747491)
I embarrassed myself as a Noogler trying to explain what in my head seemed like a good tradeoff between hash size (also of URIs) and collision handling. The process had fixed storage for a table of known hashes, and every collision was tested for validity before taking action. If you could use a truncated hash, you’d obviously increase your collisions, but if you’re going to validate all collisions anyway, it seemed like you could increase your coverage substantially (in the 60-bit case it would have been 4x) while only marginally increasing your overhead of collision handling.

There's some kind of sparsity/entropy function involved with optimizing these two but I'm too clueless to sort it out. Without the vocabulary to make my case I just got weirded out by a bunch of smart people staring at me quizzically. Sooo..

Re:There are only four billion floats, so test them all (2014) by Arcuru on Sunday October 11, 2020 @03:18PM (#24748269)
That kind of thing happens to me all the time. I'm very often unable to think of or explain things in the moment.

Sometimes it helps to write a doc afterwards to get my thoughts in order and decide if it's worth sharing.

Re:There are only four billion floats, so test them all (2014) by btrask on Sunday October 11, 2020 @05:54PM (#24749436)
It's known as the birthday paradox. There is a probability table here: https://en.wikipedia.org/wiki/Birthday_paradox#Probability_t...
Re:There are only four billion floats, so test them all (2014) by jcims on Sunday October 11, 2020 @07:16PM (#24749948)
Yes! That’s the part that I was having trouble getting my head around. Looks like 96 bits would have been fine and 128 more than adequate. A small bit of vindication :)