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
|
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 <mh.in.england@gmail.com>) id 1WRP2l-0004WV-90
for bitcoin-development@lists.sourceforge.net;
Sat, 22 Mar 2014 16:45:11 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.51 as permitted sender)
client-ip=209.85.219.51; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f51.google.com;
Received: from mail-oa0-f51.google.com ([209.85.219.51])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WRP2j-0003qP-9o
for bitcoin-development@lists.sourceforge.net;
Sat, 22 Mar 2014 16:45:11 +0000
Received: by mail-oa0-f51.google.com with SMTP id i4so3972717oah.24
for <bitcoin-development@lists.sourceforge.net>;
Sat, 22 Mar 2014 09:45:04 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.58.7 with SMTP id m7mr735385oeq.59.1395506703889; Sat, 22
Mar 2014 09:45:03 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.71.231 with HTTP; Sat, 22 Mar 2014 09:45:03 -0700 (PDT)
In-Reply-To: <CAJHLa0OK1vRiqoHDNYrbO9fNTa8tcY9dMsJ5fC0qpsHS80zvbg@mail.gmail.com>
References: <lc5hmg$1jh$1@ger.gmane.org> <leuunm$tjk$1@ger.gmane.org>
<CANEZrP3nQfvDArKTRgje0Cus4G2JD_zpxSjA3fXfxM2TNAP80Q@mail.gmail.com>
<CALDj+BafD+6KTNcYDBEu5gNPzYozSkiC-JCxrY-PzXL2DYBRsw@mail.gmail.com>
<CAJHLa0N4J_Z907+D0ENSNKfNAW2N=7Jf4JzSCO=SU558GtGTzA@mail.gmail.com>
<lge7nk$3mf$2@ger.gmane.org>
<CANEZrP0J849oDvMWjf8LWi0xj44Q8DaUwDip5_smVBMNgeQ3mw@mail.gmail.com>
<20140320121221.GA25052@netbook.cypherspace.org>
<CAJHLa0NeFdXzioQrmK6iKzr85pL3vvTAQH2_vKM3M+T+ZWYjgQ@mail.gmail.com>
<lgh47n$tnn$2@ger.gmane.org>
<CALDj+BbX+ejz+diWDGFJUyOLR6+GnbDyiiNpmEbHybNBj=jL7A@mail.gmail.com>
<CAJHLa0OK1vRiqoHDNYrbO9fNTa8tcY9dMsJ5fC0qpsHS80zvbg@mail.gmail.com>
Date: Sat, 22 Mar 2014 17:45:03 +0100
X-Google-Sender-Auth: 50yqtTjw23uiKhQOSU1uAKRbcmg
Message-ID: <CANEZrP12=cR0uWf5F_hZDwjRxMyn-DXi2n=RrYeCzXe8-Fktfg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Jeff Garzik <jgarzik@bitpay.com>
Content-Type: multipart/alternative; boundary=089e01538c565dfd1d04f534b9cd
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
X-Headers-End: 1WRP2j-0003qP-9o
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
Andreas Schildbach <andreas@schildbach.de>
Subject: Re: [Bitcoin-development] Payment Protocol for Face-to-face Payments
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: Sat, 22 Mar 2014 16:45:11 -0000
--089e01538c565dfd1d04f534b9cd
Content-Type: text/plain; charset=UTF-8
>
> Those locations are completely unsuitable to bitcoin transactions,
> since the receiver cannot verify double-spending or anything else
> about the transaction.
The usual issue is that they lack internet *for some customers*. The place
may well have private wifi or hardwired connections that work. Even mobile
networks may vary so some customers will have mobile connectivity and
others won't.
--089e01538c565dfd1d04f534b9cd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">Those locations are completely unsuitable to bit=
coin transactions,<br>
since the receiver cannot verify double-spending or anything else<br>
about the transaction.</blockquote><div><br></div><div>The usual issue is t=
hat they lack internet <i>for some customers</i>. The place may well have p=
rivate wifi or hardwired connections that work. Even mobile networks may va=
ry so some customers will have mobile connectivity and others won't.=C2=
=A0</div>
</div></div></div>
--089e01538c565dfd1d04f534b9cd--
|
