summaryrefslogtreecommitdiff
path: root/de/43f560cd895d76af02dbe2faf0191dad3cd162
blob: 73748ed782c3d494e9a37af8cf5644cbd8d44562 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <brianchoffman@gmail.com>) id 1YJTq9-0006Ck-7s
	for bitcoin-development@lists.sourceforge.net;
	Thu, 05 Feb 2015 21:19:57 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.216.173 as permitted sender)
	client-ip=209.85.216.173; envelope-from=brianchoffman@gmail.com;
	helo=mail-qc0-f173.google.com; 
Received: from mail-qc0-f173.google.com ([209.85.216.173])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1YJTq8-0005s3-6v
	for bitcoin-development@lists.sourceforge.net;
	Thu, 05 Feb 2015 21:19:57 +0000
Received: by mail-qc0-f173.google.com with SMTP id m20so8564100qcx.4
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 05 Feb 2015 13:19:50 -0800 (PST)
X-Received: by 10.140.109.55 with SMTP id k52mr277513qgf.99.1423171190767;
	Thu, 05 Feb 2015 13:19:50 -0800 (PST)
Received: from [192.168.1.3] (pool-96-255-238-248.washdc.fios.verizon.net.
	[96.255.238.248])
	by mx.google.com with ESMTPSA id e13sm406974qaw.8.2015.02.05.13.19.49
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 05 Feb 2015 13:19:49 -0800 (PST)
Content-Type: multipart/alternative;
	boundary=Apple-Mail-DD7CAC07-A104-4B7B-910C-715D1091CDEF
Mime-Version: 1.0 (1.0)
From: Brian Hoffman <brianchoffman@gmail.com>
X-Mailer: iPhone Mail (12B440)
In-Reply-To: <CANEZrP3ekWQWeV=Yw_E=n0grORBLHaXLUh3w0EFQdz=HsjWvZw@mail.gmail.com>
Date: Thu, 5 Feb 2015 16:19:47 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <279489A5-1E46-48A2-8F58-1A25821D4D96@gmail.com>
References: <CABdy8DKS4arkkCLGC=66SUJm5Ugib1EWP7B6MkQRX1k-yd3WBw@mail.gmail.com>
	<CANEZrP3v=ySS4gragaWuBMWi_swocRRRq_kw2edo6+9kifgrFQ@mail.gmail.com>
	<54D3D636.1030308@voskuil.org>
	<CANEZrP3ekWQWeV=Yw_E=n0grORBLHaXLUh3w0EFQdz=HsjWvZw@mail.gmail.com>
To: Mike Hearn <mike@plan99.net>
X-Spam-Score: -0.6 (/)
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
	(brianchoffman[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	0.0 MIME_QP_LONG_LINE RAW: Quoted-printable line longer than 76 chars
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	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
X-Headers-End: 1YJTq8-0005s3-6v
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
	Paul Puey <paul@airbitz.co>
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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 05 Feb 2015 21:19:57 -0000


--Apple-Mail-DD7CAC07-A104-4B7B-910C-715D1091CDEF
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

This sounds horrible. You could basically monitor anyone with a wallet in a h=
ighly populated area and track them super easily by doing facial recognition=
. Yes you could photograph people but it's way more burdensome. Sorry to go o=
ff topic a little.


On Feb 5, 2015, at 3:50 PM, Mike Hearn <mike@plan99.net> wrote:

>> I'm imagining myself walking around broadcasting my photo and MAC
>> address while hucksters push payment requests to me for approval
>=20
> I hate to break it to you, but you broadcast a photo of your face every ti=
me you walk outside ;)
>=20
> Bluetooth MAC addresses are random, they aren't useful identifiers. If som=
eone can see you, a face is a far more uniquely identifying thing than a MAC=
.
>=20
> "Payment spam" might be a problem. I can imagine a wallet requiring that s=
uch requests are signed and then spammers can be blacklisted in the usual fa=
shion so they can't push things to your phone anymore. Anyway, a hurdle that=
 can be jumped if/when it becomes an issue.
> --------------------------------------------------------------------------=
----
> Dive into the World of Parallel Programming. The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is yo=
ur
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a=

> look and join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development

--Apple-Mail-DD7CAC07-A104-4B7B-910C-715D1091CDEF
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>This sounds horrible. You could basica=
lly monitor anyone with a wallet in a highly populated area and track them s=
uper easily by doing facial recognition. Yes you could photograph people but=
 it's way more burdensome. Sorry to go off topic a little.</div><div><br></d=
iv><div><br></div><div>On Feb 5, 2015, at 3:50 PM, Mike Hearn &lt;<a href=3D=
"mailto:mike@plan99.net">mike@plan99.net</a>&gt; wrote:<br><br></div><blockq=
uote type=3D"cite"><div><div dir=3D"ltr"><div class=3D"gmail_extra"><div cla=
ss=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">I'm imagining myself walkin=
g around broadcasting my photo and MAC<br>
address while hucksters push payment requests to me for approval</blockquote=
><div><br></div><div>I hate to break it to you, but you broadcast a photo of=
 your face every time you walk outside ;)</div><div><br></div><div>Bluetooth=
 MAC addresses are random, they aren't useful identifiers. If someone can se=
e you, a face is a far more uniquely identifying thing than a MAC.</div><div=
><br></div><div>"Payment spam" might be a problem. I can imagine a wallet re=
quiring that such requests are signed and then spammers can be blacklisted i=
n 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.</div></div></div><=
/div>
</div></blockquote><blockquote type=3D"cite"><div><span>--------------------=
----------------------------------------------------------</span><br><span>D=
ive into the World of Parallel Programming. The Go Parallel Website,</span><=
br><span>sponsored by Intel and developed in partnership with Slashdot Media=
, is your</span><br><span>hub for all things parallel software development, f=
rom weekly thought</span><br><span>leadership blogs to news, videos, case st=
udies, tutorials and more. Take a</span><br><span>look and join the conversa=
tion now. <a href=3D"http://goparallel.sourceforge.net/">http://goparallel.s=
ourceforge.net/</a></span></div></blockquote><blockquote type=3D"cite"><div>=
<span>_______________________________________________</span><br><span>Bitcoi=
n-development mailing list</span><br><span><a href=3D"mailto:Bitcoin-develop=
ment@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a></s=
pan><br><span><a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoi=
n-development">https://lists.sourceforge.net/lists/listinfo/bitcoin-developm=
ent</a></span><br></div></blockquote></body></html>=

--Apple-Mail-DD7CAC07-A104-4B7B-910C-715D1091CDEF--