Is your world black and white? Mine isn't. So why do our computers have to be binary? The binary nature of computing makes it artificial and does not allow the robustness of natural, organic thoughts and concepts, and causes endless security vulnerabilities like this one. But Corporate America and the Republicans are stopping us at two bits, for profit. Why not ten, a hundred? As many hues as a brilliant rainbow? Life is not all ones and zeroes folks! I dogfart think it's high time we shifted our computin
It's worse than you though, in binary! 00110001001101010011100100110001001100000011001000110111
00110001001101010011100100110100001101100011001000110001
Both your UID numbers have 32 zeros and 24 ones...
It's worse than you though, in binary! [first UID in binary]
[second UID in binary]
Both your UID numbers have 32 zeros and 24 ones...
Is there a specific reason you padded them to 56 bits?
What would have made sense to me would have been no padding (no leading zeros), or padding to 64 bits (because that's how the UIDs are probably stored internally). In the first case, it would be 30 zeros, in the second, it would be 40.
BTW, how did you get it through the lame(ness) filter? I get a filter error in just quoting your post ("Filter error: That's an awful long string of letters there.") Only after removing the binary strings, Slashdot allowed
The ASCII representations of UIDs has a Hamming distance of 6, while the more logical binary representation of the UIDs has a Hamming distance of 5.
What would have made sense to me would have been no padding (no leading zeros), or padding to 64 bits (because that's how the UIDs are probably stored internally).
It's time to shift our paradigm (Score:-1, Offtopic)
Is your world black and white? Mine isn't. So why do our computers have to be binary? The binary nature of computing makes it artificial and does not allow the robustness of natural, organic thoughts and concepts, and causes endless security vulnerabilities like this one. But Corporate America and the Republicans are stopping us at two bits, for profit. Why not ten, a hundred? As many hues as a brilliant rainbow? Life is not all ones and zeroes folks! I dogfart think it's high time we shifted our computin
Re: (Score:0)
Re: (Score:3)
00110001001101010011100100110001001100000011001000110111
00110001001101010011100100110100001101100011001000110001
Both your UID numbers have 32 zeros and 24 ones...
Re: (Score:1)
It's worse than you though, in binary!
[first UID in binary]
[second UID in binary]
Both your UID numbers have 32 zeros and 24 ones...
Is there a specific reason you padded them to 56 bits?
What would have made sense to me would have been no padding (no leading zeros), or padding to 64 bits (because that's how the UIDs are probably stored internally). In the first case, it would be 30 zeros, in the second, it would be 40.
BTW, how did you get it through the lame(ness) filter? I get a filter error in just quoting your post ("Filter error: That's an awful long string of letters there.") Only after removing the binary strings, Slashdot allowed
Re:It's time to shift our paradigm (Score:1)
It's worse than you though, in binary!
[first UID in binary]
[second UID in binary]
Both your UID numbers have 32 zeros and 24 ones...
Is there a specific reason you padded them to 56 bits?
Or why he was looking at the ASCII representation of the UIDs?
A more logical representation of the numbers would be:
(00000000)000110000101010011111101
(00000000)000110000100011011110011
12 (or 20) zeros and 12 ones.
The ASCII representations of UIDs has a Hamming distance of 6, while the more logical binary representation of the UIDs has a Hamming distance of 5.
What would have made sense to me would have been no padding (no leading zeros), or padding to 64 bits (because that's how the UIDs are probably stored internally).
32 bits would be more than enough for those UIDs.