I found the Pi UUID: 185e45bc-750b-43d7-91ee-314159265358
Every V4 UUID
131–140 of 381 posts
Re: Every V4 UUID
#132Earlier quoted context omitted.
This is the biggest hack since every ATM PIN was leaked: https://pastebin.com/SmJRB8eQ
Holy shit, my PIN is on there. How the hell did that get that?? I was told it was a 1/10,000 chance of someone guessing it.
Mine too.
Takes me back to when my password was leaked:
Re: Every V4 UUID
#133I spent far too much time being childish with this, but I am quite pleased that:
69420694-2069-4206-9420-694206942069
is a valid UUID.
Re: Every V4 UUID
#134Tangentially related: HN recently (last few months) had an article explaining how large a number was. The number was something like busy beaver or 128 bit integers or something else. It illustrated how large the number was by creating activities you would do, incrementing the counter as you did them. The sequence went something like this: Walk, and every time you take a step. Add 1 After you have circled the earth, p…
The number you're thinking of is 52! (52 factorial) and how long it would take for 52! seconds to pass by. Vsauce has a great video on this, and might be where that example was taken from. https://www.youtube.com/watch?v=ObiqJzfyACM That example starts 16 minutes into the video: https://www.youtube.com/watch?v=ObiqJzfyACM&t=964s But it's worth watching the whole thing.
Yes! Nice find thank you.
Re: Every V4 UUID
#135Sometimes I feel bad when I generate a UUID without using it for anything. Like I've wasted it.
how bad do you feel about all the uuids you didnt generate so were never born?
Re: Every V4 UUID
#136wow. this is so cool
TIL aaaaaaaa-aaaa-4aaa-aaaa-aaaaaaaaaaaa is a valid uuid
Re: Every V4 UUID
#137Earlier quoted context omitted.
OH! Thanks for the precise reproduction steps, I had done my testing with a trackpad and had missed that! Writing a little fix now (I'd hate for you to not be able to see the last UUID)
> I'd hate for you to not be able to see the last UUID No spoilers, but the last one's a doozy!
Number #553752677 will surprise you!
Re: Every V4 UUID
#138It seems to skip a lot for substring search. For example if you search for 'aaaa' there's maybe 100 jumps to get to the bottom. So i'd assume that it's just a uniform random over the entire range to some limit, then filter idx > cur. But I feel like you could constrain the search more. The 'close next' should have exactly the same characters at the front. Like in your example '4AAB-' you would search valid position 14 first.
edit: actually this doesn't work because having the same start does not mean they are close together.
Re: Every V4 UUID
#139Earlier quoted context omitted.
Holy shit, my PIN is on there. How the hell did that get that?? I was told it was a 1/10,000 chance of someone guessing it.
Mine too. Takes me back to when my password was leaked: https://github.com/danielmiessler/SecLists/pull/155
could we fix this by adding '\n' to the password? then it wouldn't be guessed, the hackers would just think it was the end of the password
Re: Every V4 UUID
#140Love it! I can't help but think there's still a way to use native scrolling though. You could start with a tall document, say, 10k pixels and grab the scroll position and multiply it out when it moves to get sort of a macro scroll position. That would handle the arrows and clicking or grabbing the scroll box.
But the wheel would be tricky because you want to scroll by only one or a few items, not items/10k. With a static viewport-sized DIV set to overflow-y:scroll and large vertical content size, positioned so you don't see the scroll bar, when the mouse is over it it should capture wheel movement which you could translate to an offset from your macro scroll position.
Just a thought. Either way, love the thinking here, fun work :)