On 20/03/2017 19:05, Jacob Keller wrote:
On Sun, Mar 19, 2017 at 10:58 PM, Michael Steuer
<Michael.Steuer@xxxxxxxxxxxxxxxxx> wrote:
[..]
If base32 is being considered, I'd suggest the "base32hex" variant, which
uses the same amount of space.
I don't see the benefit of adding characters like 0 and 1 which
conflict with some of the letters? Since there's no need for a human
to decode the base32 output, it's easier to use the one that's less
likely to get screwed up when typing if that ever happens. It's not
like we actually need to know what value each character represents.
(sure the program does, but the human does not).
Thanks,
Jake
Fair enough and good point. We definitely wouldn't want 0 and O and 1
and I mixed together.
Cheers,
Mike.