I don't know if i should response to this mail list or make a comment in
operations over big numbers. This is not very fast and most of the
programming languages don't provide support for big numbers OOB.
Post by Peter Todd via bitcoin-dev
On Tue, Mar 21, 2017 at 05:16:30PM +0100, Andreas Schildbach via
Post by Andreas Schildbach via bitcoin-dev
Why use Base 32 when the QR code alphanumeric mode allows 44 characters?
"0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ$*+-./:") for most efficient QR
code encoding. I only leave out the space character because it gets
replaced by "+" in URLs.
Doing that only makes addresses a few % shorter, at the cost of
downsides. For example, not everyone knows what those additional
are called, particularly for non-English-speaking users. Non-alphanumeric
characters also complicate using the addresses in a variety of contexts
in particularly isn't valid in filenames).
I'm not convinced that transmitting addresses via voice should be a
usecase to target at. I don't understand your comment about non-english
speaking users. Obviously they cannot voice-communicate at all with
only-english-speaking users, so there is no need to communicate
voice-communicate addresses between them.
Addresses in QR codes, addresses in URLs and addresses in NFC NDEF
messages are the three most used forms.
Speaking of URLs, actually Base 32 (as well as Base 43) makes QR codes
*bigger* because due to the characters used for URL parameters (?&=)
those QR codes are locked to binary mode. To make them shorter, we'd
need to use something like "Base 64url" (or ideally Base 94 -- all
printable ASCII characters).
bitcoin-dev mailing list