News for hackers. Stuff that matters.
Re:Git 2.11 has been released by atemerev on Tuesday November 29, 2016 @05:03PM (#13066624)
Hexadecimal dumps of binary data are the worst of all worlds if used as keys/references. Hard to memorize, hard to type, look ugly, aren't compact.

Better alternatives:

Base64 without padding: compact.

Grouped decimals: slightly less compact than hexadecimal, but extremely easy to type and pronounce. E.g. 577-467-341-467

Re:Git 2.11 has been released by joallard on Tuesday November 29, 2016 @07:28PM (#13067440)
Case-insensivity is important for some to be able to reliably remember a string. I won't easily retain the difference between 'b4dQbFs31' and 'b4DqBfs31'.

Same thing when speaking it out loud. 'B four D capital Q B capital F s thirty-one' is way more convoluted and error-prone than 'B four D Q B F S thirty-one'.

The best thing I've found that fits this criterion is Crockford's Base 32 [1], basically the extension of hex digits, removing letters ILOU.

But Base 32 (case-insensitivity by proxy) constrains us to 5 bits, which is only a 20% reduction over the 4 bits of base 16. So instead of the 20 bits `1ab2f` we could express them with something like `1qm3`.

Or we could be using words...

[1]: http://www.crockford.com/wrmg/base32.html

Re:Git 2.11 has been released by eridius on Tuesday November 29, 2016 @07:55PM (#13067591)
Regarding Base 32, I love the justification used for removing U. I, L, and O all have potential confusion with digits, but U was removed because of "Accidental obscenity".
Re:Git 2.11 has been released by OJFord on Wednesday November 30, 2016 @12:09AM (#13068627)
I'm surprised it wasn't just "and all vowels" with the same reasoning, or at least 'a' (because I can more readily think of examples than for, say, 'e').

I suppose, though, there's an attraction in using b32 rather than b29... (Though I notice mid-word apostrophes are double-tap-selectable at least on macOS, so perhaps swapping 'a' for ''' would be advantageous, if more complicated to explain.)

Re:Git 2.11 has been released by eridius on Wednesday November 30, 2016 @01:40PM (#13073380)
The two "worst" swearwords that pop into mind both have "u" in them. Meanwhile, the swears with "a" in them seem to be the tamest of the lot.
Re:Git 2.11 has been released by OJFord on Wednesday November 30, 2016 @05:03PM (#13075138)
"Tameness" varies extraordinarily by region - an infamous example being 'twat' which throughout the UK ranges from friendly to vulgar.

Regardless of variance, I don't think I'd regard either the above or the name of a fat character in Austin Powers as "tamest of the lot".

Re:Git 2.11 has been released by eridius on Wednesday November 30, 2016 @05:42PM (#13075387)
I find it interesting that you're willing to say "twat" but not "bastard". I admit that I didn't think of either of those words, though I think they're still much tamer than the ones with "u" in them. Really what I was thinking of was "crap" and "damn".
Re:Git 2.11 has been released by mikeash on Tuesday November 29, 2016 @10:20PM (#13068227)
I once had a moment of panic after coming up with and shipping a custom scheme along these lines, when I realized there was a decent probability of generating accidental profanity. Afterwards I came up with a filter, and we spent a fun day filling it with every nasty word we could think of.
Re:Git 2.11 has been released by pitaj on Tuesday November 29, 2016 @09:39PM (#13068011)
That's actually pretty brilliant
Re:Git 2.11 has been released by beagle3 on Wednesday November 30, 2016 @02:06AM (#13069020)
The best way to use words that I've seen (e.g., over the phone, and also to memorize) is Mnemonicode, originally created by Oren Tirosh, who has since abandoned it, but there are multiple compatible versions all around, see e.g. [0].

Unfortunately, most of the references around the web link to Tirosh's original work on the WayBack machine, which used to be hosted on "tothink.com", but the new owners put a "robots.txt" which make even the old version unaccessible on archive.org

[0] https://github.com/singpolyma/mnemonicode

Re:Git 2.11 has been released by gabrielhn on Tuesday November 29, 2016 @05:55PM (#13066905)
Being able to easily copy/paste the string is important. The string should be a word so double clicking selects the full string. Maybe base62?
Re:Git 2.11 has been released by contingencies on Tuesday November 29, 2016 @05:48PM (#13066866)
Still better is grouped alphanumeric without potentially ambiguous characters (ie. generate number-1's but not letter-I's, generate number-0's but not letter-O's). I wrote a disambiguation library based upon the checksums present in IBAN @ https://github.com/globalcitizen/php-iban .. it's surprising how accurate the mistranscription suggestions are.

In general, pure-number systems are better if possible, but where you have issues squashing in enough data in suitably compact form, transitioning to alphanumeric is better.

You can also consider the use prefix-based systems, either utilizing temporal epochs or node-specific prefixes, both of which can utilize readable aliases.

Finally, for anything expecting human transcription, checksum systems are awesome!

Re:Git 2.11 has been released by saghm on Tuesday November 29, 2016 @07:28PM (#13067443)
> Still better is grouped alphanumeric without potentially ambiguous characters (ie. generate number-1's but not letter-I's, generate number-0's but not letter-O's)

git license-plate?

Re:Git 2.11 has been released by qznc on Tuesday November 29, 2016 @05:56PM (#13066912)
Afaik the Damm algorithm is the best for checksums https://en.wikipedia.org/wiki/Damm_algorithm