News for hackers. Stuff that matters.
Re:Updating the Git protocol for SHA-256 by marton78 on Saturday June 20, 2020 @10:41AM (#23584201)
The human friendly format you're suggesting is Douglas Crockford' Base 32 encoding.
Re:Updating the Git protocol for SHA-256 by dlkinney on Saturday June 20, 2020 @04:40PM (#23587104)
I disagree that his encoding is friendly.

I understand the compromises he made in order to make it less ambiguous, but regular users come across hashes sometimes, and unless you know it's his encoding, they're (often) smart enough to know that some characters look like others. So, when they go to recite the encoded value, they're still going to struggle "is that a 0 or an O?" etc.

We may know it doesn't make a difference, but someone who doesn't know it's explicitly his encoding (and the parameters he transposes) is still going to get hung up.

Lastly, the removal of "u" only prevents 1.5 offensive words from showing up, but I guess he chose it because he had to get rid of some letter to make it base32.

I think a base ~32 by removing all ambiguous characters and adding a non-separator punctuation mark would be ideal, frankly.

If we're worried about swear words then also remove the vowels and add 4 more punctuation mark.

IMHO

Re:Updating the Git protocol for SHA-256 by wegs on Sunday June 21, 2020 @08:23AM (#23591632)
That's a !@#$ good idea for avoiding swear words :)