3 ms·
Tested with a few UUIDs: $ uuidgen 2b2ec13b-a1a4-49da-938a-50b24a1e416a Google - https://www.google.com/search?q=2b2ec13b-a1a4-49da-938a-50b24a1e416a https:/
by nixcraft 4y ago
Tested with a few UUIDs:
$ uuidgen
2b2ec13b-a1a4-49da-938a-50b24a1e416a
Google - https://www.google.com/search?q=2b2ec13b-a1a4-49da-938a-50b24a1e416a https://www.google.com/search?q=2b2ec13b-a1a4-49da-938a-50b2...
$ uuidgen --sha1 --namespace @dns --name "www.google.com"
488416f4-fcaf-5027-8c63-0105cfa213ea
Google - https://www.google.com/search?q=488416f4-fcaf-5027-8c63-0105cfa213ea https://www.google.com/search?q=488416f4-fcaf-5027-8c63-0105...
Nothing. Maybe it is a bug?
- hbbio 4y agoNot a bug, there are actual search results for the last query. So probably a feature that since results exist, it's not a computation.
- tomxor 4y agoThose aren't valid expressions. It's when there aren't any numerals after a letter, then the letters can be interpreted as variables and the numerals coefficients (for each term separated by a subtract).
- deleted 4y ago[deleted]
- jwilk 4y agoThat's not it. Digits after letter didn't stop Google from interpreting the original UUID.
- tomxor 4y agoOh you're right. it just considers them all multiplications, sometimes powers. Only other difference I can see then is >1 contiguous letters in the UUIDS that didn't trigger it, maybe variables have to be single letter.