Re: [Cbor] CBOR in QRcodes

Michael Richardson <> Thu, 24 June 2021 00:55 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B28CE3A172B for <>; Wed, 23 Jun 2021 17:55:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id sSj_CiwwUFmT for <>; Wed, 23 Jun 2021 17:55:28 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D0EEA3A172A for <>; Wed, 23 Jun 2021 17:55:27 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTPS id 6F82E1F455; Thu, 24 Jun 2021 00:55:24 +0000 (UTC)
Received: by (Postfix, from userid 179) id ED4A51A01E3; Wed, 23 Jun 2021 20:55:22 -0400 (EDT)
From: Michael Richardson <>
To: Christian =?us-ascii?Q?=3D=3Fiso-8859-1=3FQ=3FAms=3DFCss=3F=3D?= <>,
In-reply-to: <YNN05Efh4/>
References: <9704.1624378576@localhost> <YNN05Efh4/>
Comments: In-reply-to Christian =?us-ascii?Q?=3D=3Fiso-8859-1=3FQ=3FAms=3D?= =?us-ascii?Q?FCss=3F=3D?= <> message dated "Wed, 23 Jun 2021 19:52:36 +0200."
X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Wed, 23 Jun 2021 20:55:22 -0400
Message-ID: <19914.1624496122@dooku>
Archived-At: <>
Subject: Re: [Cbor] CBOR in QRcodes
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 24 Jun 2021 00:55:33 -0000

Christian Amsüss <> wrote:
    > binary data that is not UTF-8. The dispatch into apps of the OS appears
    > to be focused around interpreting the QR code values as URIs and then
    > registering prefixes (which may not be registered schemes but look like
    > them, or may be schemes including host names) for an installed app (or
    > even to go into the app store).

Android's intent system can handle binary data, but quite possibly the way
that the stock QRcode reader works, that can never make it in.

I guess if one intends to make the COVID certificate usable across the widest
number of scanners, then it needs to be ASCII happy.   So from bouncers at
night clubs with throw-away 2013 era iPhone3s, to PCs running 3270 emulators
at the immigration booth.

I'm sure that a custom QRcode app could process binary if it didn't intend to
dispatch through android intents.

For reasons too stupid to explain, I actually have been walking around with
Avery labels with some self-generated QRcodes in my laptop bag for like two years.
I should see if I can convince some small store with a scanner to let me scan
my QRcode, with Notepad open, and see what happens.

I suspect that the keyboard interface is the critical, smallest path for
QRcode input.

]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]        |   ruby on rails    [