3 ms·
I've seen QR codes to join a discord that have text under them that looks like discord.gg/{... a few random characters ...} which are just fine to scan or
by PaulHoule 2y ago
I've seen QR codes to join a discord that have text under them that looks like
discord.gg/{... a few random characters ...}
which are just fine to scan or type in.
My own 'discovery' about QR codes a few years is that you can make them "module 2" sized that ought to be easy to read with a low-spec system and have astronomical capacity if you use uppercase characters, a reasonably short domain and identifiers similar to random UUIDs. These were part of the system of "three-sided cards"
https://mastodon.social/@UP8/111013706271196029 https://mastodon.social/@UP8/111013706271196029
but new-style cards put the QR code in front because (1) I have a huge amount of glossy paper that I can't print on the back of, (2) you can't read the QR code on the back if the card is stuck to the wall with mounting putting, (3) three-sided cards struggled with branding in that people didn't really understand the affordances they offered, a problem that the new-style cards attack in various ways.
https://mastodon.social/@UP8/113541119391897096 https://mastodon.social/@UP8/113541119391897096
(Note the QR codes on both of those cards do not point at safebooru but at a redirect that I control that fits my QRL specification)
Personally I don't think any QR code for the web should ever require more than a "module 2" QR code and that printing a QR code which requires extra alignment markers is a sign of failure. (e.g. sure you can make a QR-code with 2000 bytes of form data embedded in it, but should you? Random UUIDs are so numerous and redirects so cheap that every new-style card like that Yakumo Ran card has a unique id because with inkjet printing it doesn't cost anything more)