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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1YL8gY-00005H-Hk
for bitcoin-development@lists.sourceforge.net;
Tue, 10 Feb 2015 11:08:54 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.54 as permitted sender)
client-ip=74.125.82.54; envelope-from=mh.in.england@gmail.com;
helo=mail-wg0-f54.google.com;
Received: from mail-wg0-f54.google.com ([74.125.82.54])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YL8gW-0000Ho-MK
for bitcoin-development@lists.sourceforge.net;
Tue, 10 Feb 2015 11:08:54 +0000
Received: by mail-wg0-f54.google.com with SMTP id y19so6545007wgg.13
for <bitcoin-development@lists.sourceforge.net>;
Tue, 10 Feb 2015 03:08:46 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.194.61.51 with SMTP id m19mr51801001wjr.39.1423566526541;
Tue, 10 Feb 2015 03:08:46 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.194.188.11 with HTTP; Tue, 10 Feb 2015 03:08:46 -0800 (PST)
In-Reply-To: <CAAt2M188whrv9VgV8UYBq+kcmgN9b6QQH7+wd7wQYNj8bd4Pcg@mail.gmail.com>
References: <CAAt2M18H0K99bmD4H_FRSeE+O9nGFDruCmo63GOQt1kxAdVBmQ@mail.gmail.com>
<CAAt2M188whrv9VgV8UYBq+kcmgN9b6QQH7+wd7wQYNj8bd4Pcg@mail.gmail.com>
Date: Tue, 10 Feb 2015 12:08:46 +0100
X-Google-Sender-Auth: Kezxaq0iGcPUT8kgCccO8JBTIVw
Message-ID: <CANEZrP2LhgFWWJYQGO+XbDX1o5=hwPtFbE+etEHoQo+3AfUSrA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Natanael <natanael.l@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b66fa5f20f793050eb9e938
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: 1YL8gW-0000Ho-MK
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Standardizing automatic pre-negotiation
of transaction terms with BIP70? (Emulating Amazon one-click purchase at
all merchants)
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: Tue, 10 Feb 2015 11:08:54 -0000
--047d7b66fa5f20f793050eb9e938
Content-Type: text/plain; charset=UTF-8
We can certainly imagine many BIP70 extensions, but for things like
auto-filling shipping addresses, is the wallet the best place to do it? My
browser already knows how to fill out this data in credit card forms, it
would make sense to reuse that for Bitcoin.
It sounds like you want a kind of Star-Trek negotiation agent thing, where
your computer knows how to seek out the best deal because all the metadata
is standardised. Such a thing would be an interesting project, but it's
probably not best done in BIP70 given how it's deployed and used today.
Rather, I'd suggest looking at the various HTML5 data standards which would
allow merchants to advertise things like where they ship to in a machine
readable and crawlable form.
--047d7b66fa5f20f793050eb9e938
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra">We can certainly imagine many B=
IP70 extensions, but for things like auto-filling shipping addresses, is th=
e wallet the best place to do it? My browser already knows how to fill out =
this data in credit card forms, it would make sense to reuse that for Bitco=
in.</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">It=
sounds like you want a kind of Star-Trek negotiation agent thing, where yo=
ur computer knows how to seek out the best deal because all the metadata is=
standardised. Such a thing would be an interesting project, but it's p=
robably not best done in BIP70 given how it's deployed and used today. =
Rather, I'd suggest looking at the various HTML5 data standards which w=
ould allow merchants to advertise things like where they ship to in a machi=
ne readable and crawlable form.</div></div>
--047d7b66fa5f20f793050eb9e938--
|
