From: Frantisek Borsik <frantisek.borsik@gmail.com>
To: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] QR codes on the move
Date: Sat, 14 Oct 2023 19:14:27 +0200 [thread overview]
Message-ID: <CAJUtOOgPPTY3Co-usJ7x3qoFkvU=p9tX-L9SUQzGgSCB_0-KaQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5MsaC+ysxzanqg1ykGmXCp2VNpw4=R3LdCqD=BTszqkA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]
I guess that at least 1/4 of it would be people trying to find out what it
is with their smartphone cameras.
I scan QR codes I see if it looks like it may lead to something interesting…
All the best,
Frank
Frantisek (Frank) Borsik
https://www.linkedin.com/in/frantisekborsik
Signal, Telegram, WhatsApp: +421919416714
iMessage, mobile: +420775230885
Skype: casioa5302ca
frantisek.borsik@gmail.com
On Sat, 14 Oct 2023 at 6:59 PM, Dave Taht via Nnagain <
nnagain@lists.bufferbloat.net> wrote:
> https://twitter.com/Laughing_Mantis/status/1710043283295256812
>
> "Traveling with a custom made QR code visible on a bag or clothing
> between 2 airports and 2 countries reveals 16 unique scans over 96
> hours"
>
> I know there are a lot of cameras out there, but holy cow. This of
> course does not count the stuff that can read a chip card at distance.
>
> --
> Oct 30:
> https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
> Dave Täht CSO, LibreQos
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
>
[-- Attachment #2: Type: text/html, Size: 2252 bytes --]
prev parent reply other threads:[~2023-10-14 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-14 16:59 Dave Taht
2023-10-14 17:14 ` Frantisek Borsik [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/nnagain.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJUtOOgPPTY3Co-usJ7x3qoFkvU=p9tX-L9SUQzGgSCB_0-KaQ@mail.gmail.com' \
--to=frantisek.borsik@gmail.com \
--cc=nnagain@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox