Linus on Git and SHA-1

Re:Linus on Git and SHA-1 by runeks on Saturday February 25, 2017 @05:12PM (#13734165)

Then you have stuff like 1, I and l, which are difficult to distinguish. Which was why base58 was invented (basically the range you suggested, without visually similar characters).

[ Parent | on HN ]

Re:Linus on Git and SHA-1 by derefr on Saturday February 25, 2017 @07:29PM (#13734829)

And zbase32 (https://philzimmermann.com/docs/human-oriented-base-32-encod...), which is my own preference for still being case-insensitive and thereby able to be used in subdomain names or email addresses.

[ Parent | on HN ]

Re:Linus on Git and SHA-1 by kzrdude on Saturday February 25, 2017 @05:16PM (#13734177)

This really should not be a problem since that's task #1 that a programmer's good font needs to solve.

[ Parent | on HN ]

Re:Linus on Git and SHA-1 by cbr on Saturday February 25, 2017 @06:56PM (#13734693)

I often run into git hashes places where a programming font wouldn't apply, like URLs and web pages.

[ Parent | on HN ]

Re:Linus on Git and SHA-1 by wongarsu on Saturday February 25, 2017 @07:17PM (#13734783)

>where a programming font wouldn't apply, like URLs

Any phisher's wet dream is a URL displayed in a font where l and I look the same. For anything that routinely displays URLs, font matters a lot. And any website displaying git hashes is likely to be programming related and have some code-font (good monospace or similar) in it's repertoir.

[ Parent | on HN ]