At least v4 will use Java's SecureRandom, and my server is running a recent Oracle JVM7, so I would argue that the randomness should be decent enough. Maybe not perfect, but good enough to make collisions extremely unlikely.
That being said, this service really was written as joke. Particularly the JSON and XML outputs.
As to /dev/random, no, it's not simply derived from time between hard drive seeks (at least for the operating systems I care about).
One can use http://uuid.me/v1.json or http://uuid.me/v4.json
At least v4 will use Java's SecureRandom, and my server is running a recent Oracle JVM7, so I would argue that the randomness should be decent enough. Maybe not perfect, but good enough to make collisions extremely unlikely.
That being said, this service really was written as joke. Particularly the JSON and XML outputs.
As to /dev/random, no, it's not simply derived from time between hard drive seeks (at least for the operating systems I care about).