From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YJU6K-0005Bs-Dx for bitcoin-development@lists.sourceforge.net; Thu, 05 Feb 2015 21:36:40 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.52 as permitted sender) client-ip=74.125.82.52; envelope-from=mh.in.england@gmail.com; helo=mail-wg0-f52.google.com; Received: from mail-wg0-f52.google.com ([74.125.82.52]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YJU6I-0006cl-Uq for bitcoin-development@lists.sourceforge.net; Thu, 05 Feb 2015 21:36:40 +0000 Received: by mail-wg0-f52.google.com with SMTP id y19so9939217wgg.11 for ; Thu, 05 Feb 2015 13:36:33 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.180.7.199 with SMTP id l7mr504400wia.66.1423172192974; Thu, 05 Feb 2015 13:36:32 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.194.188.11 with HTTP; Thu, 5 Feb 2015 13:36:32 -0800 (PST) In-Reply-To: <279489A5-1E46-48A2-8F58-1A25821D4D96@gmail.com> References: <54D3D636.1030308@voskuil.org> <279489A5-1E46-48A2-8F58-1A25821D4D96@gmail.com> Date: Thu, 5 Feb 2015 22:36:32 +0100 X-Google-Sender-Auth: ni2QRUDXQaXcNsGigiHQkJBRo88 Message-ID: From: Mike Hearn To: Brian Hoffman Content-Type: multipart/alternative; boundary=f46d044404900440f8050e5e1942 X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.0 AWL AWL: Adjusted score from AWL reputation of From: address X-Headers-End: 1YJU6I-0006cl-Uq Cc: Bitcoin Dev , Paul Puey Subject: Re: [Bitcoin-development] Proposal for P2P Wireless (Bluetooth LE) transfer of Payment URI X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Feb 2015 21:36:40 -0000 --f46d044404900440f8050e5e1942 Content-Type: text/plain; charset=UTF-8 > > This sounds horrible. You could basically monitor anyone with a wallet in > a highly populated area and track them super easily by doing facial > recognition. > We're talking about BLE, still? The radio tech that runs in the so called "junk bands" because propagation is so poor? My watch loses its connection to my phone if I just put it down and walk around my apartment. I'm all for reasonable paranoia, but Bluetooth isn't going to be enabling mass surveillance any time soon. It barely goes through air, let alone walls. Anyway, whatever. I'm just bouncing around ideas for faster user interfaces. You could always switch it off or set it to be triggered by the presence of particular wifi hotspots, if you don't mind an initial bit of setup. Back on topic - the debate is interesting, but I think to get this to the stage of being a BIP we'd need at least another wallet to implement it? Then I guess a BIP would be useful regardless of the design issues. The prefix matching still feels flaky to me but it's hard to know if you could really swipe payments out of the air in practice, without actually trying it. --f46d044404900440f8050e5e1942 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
This sounds horrible. You= could basically monitor anyone with a wallet in a highly populated area an= d track them super easily by doing facial recognition.

We're talking about BLE, still? The radio tech = that runs in the so called "junk bands" because propagation is so= poor?

My watch loses its connection to my phone i= f I just put it down and walk around my apartment. I'm all for reasonab= le paranoia, but Bluetooth isn't going to be enabling mass surveillance= any time soon. It barely goes through air, let alone walls.

=
Anyway, whatever. I'm just bouncing around ideas for faster = user interfaces. You could always switch it off or set it to be triggered b= y the presence of particular wifi hotspots, if you don't mind an initia= l bit of setup.

Back on topic - the debate is inte= resting, but I think to get this to the stage of being a BIP we'd need = at least another wallet to implement it? Then I guess a BIP would be useful= regardless of the design issues. The prefix matching still feels flaky to = me but it's hard to know if you could really swipe payments out of the = air in practice, without actually trying it.


<= /div>
--f46d044404900440f8050e5e1942--