3 ms·
Note, though, that content of a length sufficient to result in that performance degradation would not be "human-friendly" — and thus, not a viable use case for
by floatingatoll 6y ago
Note, though, that content of a length sufficient to result in that performance degradation would not be "human-friendly" — and thus, not a viable use case for Base32H as it's specified here — no matter whether a 32 or 53 or whatever-base encoding scheme is used.
(Technically, a book can be considered 'human friendly', but that's not the definition OP is using for that phrase, either.)
- yellowapple 6y agoTo be clear, long Base32H numbers are definitely in scope (which is why the specification "recommends" a binary encoding scheme for this exact purpose, and why things like public keys/signatures are mentioned among the proposed use cases). Yeah, it'd suck for a human to have to manually record or dictate large-ish (more than 1kb / 1600 digits) sets of data, but it sucks at least a little bit less when you already know that everything can be assumed to be uppercase.