Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YJTOE-0004T9-Ep for bitcoin-development@lists.sourceforge.net; Thu, 05 Feb 2015 20:51:06 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.48 as permitted sender) client-ip=74.125.82.48; envelope-from=mh.in.england@gmail.com; helo=mail-wg0-f48.google.com; Received: from mail-wg0-f48.google.com ([74.125.82.48]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YJTOD-0006F0-Bm for bitcoin-development@lists.sourceforge.net; Thu, 05 Feb 2015 20:51:06 +0000 Received: by mail-wg0-f48.google.com with SMTP id x12so9761840wgg.7 for ; Thu, 05 Feb 2015 12:50:59 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.180.99.137 with SMTP id eq9mr137012wib.34.1423169459304; Thu, 05 Feb 2015 12:50:59 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.194.188.11 with HTTP; Thu, 5 Feb 2015 12:50:59 -0800 (PST) In-Reply-To: <54D3D636.1030308@voskuil.org> References: <54D3D636.1030308@voskuil.org> Date: Thu, 5 Feb 2015 21:50:59 +0100 X-Google-Sender-Auth: HszZwHemieYoprl92H3OXybFHKo Message-ID: From: Mike Hearn To: Eric Voskuil Content-Type: multipart/alternative; boundary=f46d04428f3e13bf07050e5d76cf 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: 1YJTOD-0006F0-Bm 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 20:51:06 -0000 --f46d04428f3e13bf07050e5d76cf Content-Type: text/plain; charset=UTF-8 > > I'm imagining myself walking around broadcasting my photo and MAC > address while hucksters push payment requests to me for approval I hate to break it to you, but you broadcast a photo of your face every time you walk outside ;) Bluetooth MAC addresses are random, they aren't useful identifiers. If someone can see you, a face is a far more uniquely identifying thing than a MAC. "Payment spam" might be a problem. I can imagine a wallet requiring that such requests are signed and then spammers can be blacklisted in the usual fashion so they can't push things to your phone anymore. Anyway, a hurdle that can be jumped if/when it becomes an issue. --f46d04428f3e13bf07050e5d76cf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I'm imagining myself walking around broadcas= ting my photo and MAC
address while hucksters push payment requests to me for approval

I hate to break it to you, but you broadcast a photo = of your face every time you walk outside ;)

Blueto= oth MAC addresses are random, they aren't useful identifiers. If someon= e can see you, a face is a far more uniquely identifying thing than a MAC.<= /div>

"Payment spam" might be a problem. I can= imagine a wallet requiring that such requests are signed and then spammers= can be blacklisted in the usual fashion so they can't push things to y= our phone anymore. Anyway, a hurdle that can be jumped if/when it becomes a= n issue.
--f46d04428f3e13bf07050e5d76cf--