Earlier quoted context omitted.
Nerd hacker politics, but SSN leaks are no joke.
I had a database of all SSNs for a while, but it was on a work laptop, so I didn't get to keep it.
Here you go; every SSN: https://github.com/panzertime/every_ssn
Every V4 UUID
331–340 of 381 posts
Re: Every V4 UUID
#332Earlier quoted context omitted.
Yeah, I at first, I though I knew exactly how it worked. Then I saw the search field, and I suddenly had no idea what the hell was going on. Now, the big question, do I want to spoil the magic trick and read how this was done, or should I keep being astonished and flabbergasted?
If you're an Everettian, roll https://www.jrussellhuffman.com/quantumdice/ and read it only if the die is odd. You can have your cake and eat it too.
Genius.
Re: Every V4 UUID
#333I'd like to announce my new `npm` package called `get-uuid`. Behind the scenes, it loads `everyuuid.com`, picks a random row number, and returns that UUID.
Could you please add a function to check if a uuid exists?
Re: Every V4 UUID
#334Earlier quoted context omitted.
I did some fooling around with this and it seems promising. The first problem is that, when your enciphering function is a matrix, f(0) = 0. This looks bad, but we can easily solve that problem by starting the webpage sequence at an index higher than 0. I tried to work through a much smaller version of the problem* by hand, and it looks like this: We have our enciphering matrix N: [[1 1 1 1 1] [1 0 0 1 1] [1 1 1 0 0]…
Following up, using this encipherment scheme and starting from a 5-bit seed of 17, you produce values in this sequence: 5, 7, 31, 10, 18, 16, 8, 11, 19, 17, 9, 28, 4, 6, 30, 0, 24, 26, 2, 23, 15, 13, 21, 22, 14, 12, 20, 1, 25, 27, 3, 29. This might pass an eyeball test for random when viewed as decimal numbers. (Although there sure are a lot of cases where adjacent values are 2 apart!) It looks much worse as binary.…
correction: the run of the eights is 3332cccd, not 3332bbbc.
Re: Every V4 UUID
#335It seems that 00000000-0000-4000-8000-000000000000 is the "smallest" UUID generated by 2645248903793120745936665251644898482.
Re: Every V4 UUID
#336> Browsers do not want to render a window that is over a trillion trillion pixels high, so I needed to handle scrolling and rendering on my own What’s fun is what actually happens when you try to do these things. It’s disappointing, you can’t even get anywhere near one trillion pixels. The limits I found five years ago when working at Fastmail, after a customer using IE found their scrollbar broke when they had aroun…
Ah this is great - I tried finding a modern-ish list of max browser heights while writing the blog. Do you mind if I link your comment in an update?
(I'm also super curious how those numbers were chosen and about what would start breaking if the limits weren't there - maybe your example of weirdness around clientHeight etc gets at that)
Re: Every V4 UUID
#337> It’s a little awkward to take our two chunks of 61 bits and map it onto the available bits here.
Does it say anything about code-AI that a problem which should be (is!) very easy for machines, but very difficult for front-endy people, seems to also be very difficult for Claude?
Re: Every V4 UUID
#338These were all, of course, already available in Borges' library.
Re: Every V4 UUID
#339What am I missing here? What is the purpose of this?
Re: Every V4 UUID
#340Earlier quoted context omitted.
If you're going by hex, the biggest UUID is entirely f's, 32 of them. It's defined specially and doesn't have version or variant.
I see what you mean, but I was going by the definition of "UUID" used on everyuuid.com. The UUID of 32 "f's" isn't in the list.
[deleted]