Alternative title: "I made my shuffle function dependent on the US government...".
... with predictable results. I use the NIST Randomness Beacon pulse for a provably and auditably random assignment of tournament contestants. While debugging my little project, I noticed that the shuffler (yeah for Fisher-Yates!) kept producing the same output over and over again. Turns out it wasn't my ineptitude ... but the guys and gals in Maryland were to blame. Go figure.
I have since been made aware of CURBy, the randomness beacon issued by the University of Colorado in Boulder, https://random.colorado.edu/software.
I shall implement this as a back-up solution whenever NIST is not available.
Alternative title: "I made my shuffle function dependent on the US government...".
... with predictable results. I use the NIST Randomness Beacon pulse for a provably and auditably random assignment of tournament contestants. While debugging my little project, I noticed that the shuffler (yeah for Fisher-Yates!) kept producing the same output over and over again. Turns out it wasn't my ineptitude ... but the guys and gals in Maryland were to blame. Go figure.
I have since been made aware of CURBy, the randomness beacon issued by the University of Colorado in Boulder, https://random.colorado.edu/software.
I shall implement this as a back-up solution whenever NIST is not available.