Difference between revisions of "User talk:Claribanter"

From Geohashing
imported>Robyn
(Did you figure it out?)
imported>Claribanter
Line 4: Line 4:
  
 
hey, did you solve the problem already?  What was the answer? I was curious. -[[User:Robyn|Robyn]] 00:52, 3 April 2009 (UTC)
 
hey, did you solve the problem already?  What was the answer? I was curious. -[[User:Robyn|Robyn]] 00:52, 3 April 2009 (UTC)
 +
 +
 +
Yup, crisis averted! Turns out, that a fractional hexadecimal number is different than just a hexadecimal number. The algorithm doesn't just prepend a 0 before the hexadecimal number that is generated by the MD5 hash, that 0 actually changes the number into a fractional hexadecimal number. So it turns a plain old integer hexadecimal number into a hexadecimal fraction and then converts that hexadecimal fraction into a decimal number. Since hex is in base 16 and decimal is base 10 fractions work a little differently. -[[User:Claribanter|Claribanter]] 23:53, 02 April 2009 (UTC)

Revision as of 01:03, 3 April 2009

I don't know the answer to your question, but recommend you post your Main Page question on Talk:The Algorithm and/or Talk:Implementations to best get the attention of those who can answer it. -Robyn 23:37, 2 April 2009 (UTC)

Thanks Robyn. -Claribanter 23:53, 02 April 2009 (UTC)

hey, did you solve the problem already? What was the answer? I was curious. -Robyn 00:52, 3 April 2009 (UTC)


Yup, crisis averted! Turns out, that a fractional hexadecimal number is different than just a hexadecimal number. The algorithm doesn't just prepend a 0 before the hexadecimal number that is generated by the MD5 hash, that 0 actually changes the number into a fractional hexadecimal number. So it turns a plain old integer hexadecimal number into a hexadecimal fraction and then converts that hexadecimal fraction into a decimal number. Since hex is in base 16 and decimal is base 10 fractions work a little differently. -Claribanter 23:53, 02 April 2009 (UTC)