News for hackers. Stuff that matters.
Re:Updating the Git protocol for SHA-256 by yencabulator on Saturday June 20, 2020 @04:37PM (#23587084)
The larger alphabet codes are unwieldy to type/read out loud. Past 10+26=36 you run out of decent symbols (making case significant is not user fiendly), and even in that range you have confusing pairs like 1iI 0o.

My personal favorite is z-base-32. It has none of those issues, and is much more compact than hex. It's the perfect in-between.

http://philzimmermann.com/docs/human-oriented-base-32-encodi...

Re:Updating the Git protocol for SHA-256 by kzrdude on Saturday June 20, 2020 @06:13PM (#23587817)
Base-32 just encodes one more bit per symbol (5 instead of the 4 per symbol that hex does), so the improvement is rather minor.
Re:Updating the Git protocol for SHA-256 by yencabulator on Sunday June 21, 2020 @09:06PM (#23596607)
52 characters vs 64 characters for a 32-byte public key is a decent improvement if you ask me. Or, more to the point, aiming for anything denser makes the alphabet less friendly.