Live data from Hacker News

Show HN: Base24 binary-to-text encoding for humans

kuon.ch

61–69 of 69 posts

Re: Show HN: Base24 binary-to-text encoding for humans

#62
post #17
post #6

Though clearly there are some advantages with removing ambiguous chars... I feel like it's more of a UI / UX thing-to-polish than a problem . Lack of polish creates the problem, the ambiguous chars themselves are not inherently an issue. If it's ambiguous, you could accept either and transform it to the correct value (implicitly, or as entered, or whenever makes sense. your users don't ever have to know). Or if you c…

> do something like 1password does with chars and letters: show them differently That’s missing the point. You can show them differently, but the point of keys / recovery codes is that they’ll be stored somewhere and later re-entered. Users could store them in any program (including writing them down or printing them out), you can’t control how they are displayed over there. Then when they need to use them, there’s a…

Since you can't control the display there, but you can control how it's interpreted, you make it a non-issue by mapping them to the same thing in whatever is consuming the input.

Or just try all combinations, unless they entered o0o0o0o0o0o0o0o0o0o0o0 you're probably only going to have to try a small handful.

Re: Show HN: Base24 binary-to-text encoding for humans

#64
post #4

Microsoft product keys were base-24 with the following alphabet: > B C D F G H J K M P Q R T V W X Y 2 3 4 6 7 8 9 they were 115 bits encoded in 24 characters see also human-oriented base32 encoding: https://philzimmermann.com/docs/human-oriented-base-32-encod... which includes this nice trick: > We have permuted the alphabet to make the more commonly occuring characters also be those that we think are easier to read…

> edit: to add, an interesting human-readable and memorable base52 alphabet that I've never found a use for is to use playing cards

The most famous example is Schneier's Solitaire [1]. It was a common encoding I liked to play with in HS classes even before reading Cryptonomicon. I still think about it sometimes when I read through a Duplicate Bridge story in that long syndicated newspaper column. (One of these days I will actually learn Bridge, maybe.)

[1] https://www.schneier.com/academic/solitaire/

Re: Show HN: Base24 binary-to-text encoding for humans

#65
post #61

What about Base10 emoji encoding? There is already more than 1024 of them ;) 128bit can be then represented by just 13 characters, or even much less with modifiers.

It's certainly a fun idea. If the goal is human readable, humans are surprisingly bad at differentiating emoji just by looking at them, especially all of the subtly different variation face ones. Describing them over something like a phone call could lead to all sorts of transcription mistakes. Not to mention that there's a variety of different emoji input systems/keyboards and the amount of user skill in finding/picking emoji for text entry are hugely variable.

Re: Show HN: Base24 binary-to-text encoding for humans

#66
mod 24 isn't a field, so it's not easy to add good error protection to base24 using a regular cyclic code.

You can add a single check digit with good performance using the Damm algorithm: https://en.wikipedia.org/wiki/Damm_algorithm one of the external links on that article has a suitable quasigroup matrix for Z_24.

Re: Show HN: Base24 binary-to-text encoding for humans

#68
post #45
post #40

Earlier quoted context omitted.

That's what the NATO phonetic alphabet is for.

In this case the phonetic alphabet will do the job only for English-speaking countries (or at least those that are very well accustomed to Latin characters).

The point of the NATO alphabet is everyone in NATO uses it, even if it isn't their native alphabet, as in the case of Greece.
Post reply on HN