News for hackers. Stuff that matters.
Re:Base58 by decentralised on Thursday November 08, 2018 @12:19PM (#18407894)
Why base-58 instead of standard base-64 encoding?

- Don't want 0OIl characters that look the same in some fonts and could be used to create visually identical looking data.

- A string with non-alphanumeric characters is not as easily accepted as input.

- E-mail usually won't line-break if there's no punctuation to break at.

- Double-clicking selects the whole string as one word if it's all alphanumeric.

https://github.com/bitcoin/bitcoin/blob/master/src/base58.h

Re:Base58 by athenot on Thursday November 08, 2018 @01:02PM (#18408299)
This is a similar encoding as airline reservation numbers, except it also has lowercase characters. But the requirements are very similar. It's amazing how much confusion is removed by suppressing ambiguities between number 0 vs. letter O and number 1 vs. letter I.

For reservation numbers, doing away with case makes it easier to speak the number over the phone.

Re:Base58 by decentralised on Friday November 09, 2018 @02:37AM (#18412925)
It's amazing how user experience can be affected from this deep in the stack.
Re:Base58 by kulahan on Monday November 12, 2018 @02:53PM (#18435149)
It might be interesting to see a form of encoding that removes similar-sounding letters/numbers as well. No more "A" or "J", "B" or "D", "3" or "T" confusion. Just stuff with a distinct sound!
Re:Base58 by jimktrains2 on Thursday November 08, 2018 @08:23PM (#18411679)
Crockford base32?
Re:Base58 by strainer on Thursday November 08, 2018 @02:35PM (#18409204)
Knocking out similar characters is a good idea but could be done to base32 to make it a little handier. I don't feel adding case sensitivity is worth a 15% reduction in string length.