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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
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 1WW5Sc-0001rY-3S
for bitcoin-development@lists.sourceforge.net;
Fri, 04 Apr 2014 14:51:14 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.43 as permitted sender)
client-ip=209.85.219.43; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f43.google.com;
Received: from mail-oa0-f43.google.com ([209.85.219.43])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WW5Sb-0006iA-7G
for bitcoin-development@lists.sourceforge.net;
Fri, 04 Apr 2014 14:51:14 +0000
Received: by mail-oa0-f43.google.com with SMTP id eb12so3655496oac.16
for <bitcoin-development@lists.sourceforge.net>;
Fri, 04 Apr 2014 07:51:07 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.135.226 with SMTP id pv2mr1761487oeb.62.1396623067760;
Fri, 04 Apr 2014 07:51:07 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.96.180 with HTTP; Fri, 4 Apr 2014 07:51:07 -0700 (PDT)
In-Reply-To: <CA+WZAEqREDkDvmhM7AY+Ju3fkm3uOGm39Ef9+SYoEr43ybbg2Q@mail.gmail.com>
References: <CA+WZAEp3HsW5ESGUZ7YfR1MZXGC5jd+LucUt_MUP8K94Xwhuhg@mail.gmail.com>
<CANEZrP0KVyp2Va7Wyy=t0qYkLNK9BDUaSzBfuzQss+=weLJ1Fw@mail.gmail.com>
<CA+WZAEqYKv8T1OMCKhOJvf5FAy=WujJ=OhtsYP9aBf=4ZPNxmw@mail.gmail.com>
<CANEZrP0DTYqobECBbw6eZqdk+-TR_2jhBtOviN08r31EQGmZHQ@mail.gmail.com>
<CANEZrP2Z5x0_kOQ=8-BMzbmi9=D=ou=s3dgEksMA5F84BHSt9A@mail.gmail.com>
<CA+WZAEqREDkDvmhM7AY+Ju3fkm3uOGm39Ef9+SYoEr43ybbg2Q@mail.gmail.com>
Date: Fri, 4 Apr 2014 16:51:07 +0200
X-Google-Sender-Auth: tAVK7syGBaQ0RwE60_dpjQbCkPc
Message-ID: <CANEZrP15xWWq2jU5yKjG+9hp___OovtbH+vM5KkzFcaQ=koRow@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: =?UTF-8?Q?Eric_Larchev=C3=AAque?= <elarch@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b4142c6d6d10904f638a509
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: 1WW5Sb-0006iA-7G
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Draft BIP for seamless website
authentication using Bitcoin address
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: Fri, 04 Apr 2014 14:51:14 -0000
--047d7b4142c6d6d10904f638a509
Content-Type: text/plain; charset=UTF-8
>
> My view on this is mainly about the UX and the fact everyone in
> Bitcoinland has a wallet.
>
Well, yes, but we also have browsers too :)
I don't want to suggest the problem is unimportant - I'd love it if the
world could move beyond passwords. But I have many scars from my time in
the Google account swamps. We had a big team, lots of resources and even
just getting people to use their phone as a second factor - *the simplest
second factor possible* - was a huge uphill battle that most users just
didn't care about. People like passwords. If you can find a way to make
something that's better than a password but just as convenient, fantastic!
But I don't think Bitcoin addresses are such a thing.
--047d7b4142c6d6d10904f638a509
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"><div dir=3D"ltr"><div class=3D"gmail_extra"><div=
class=3D"gmail_quote">
<div class=3D""><div>My view on this is mainly about the UX and the fact ev=
eryone in Bitcoinland has a wallet.<br></div></div></div></div></div></bloc=
kquote><div><br></div><div>Well, yes, but we also have browsers too :)=C2=
=A0</div>
<div><br></div><div>I don't want to suggest the problem is unimportant =
- I'd love it if the world could move beyond passwords. But I have many=
scars from my time in the Google account swamps. We had a big team, lots o=
f resources and even just getting people to use their phone as a second fac=
tor - <i>the simplest second factor possible</i>=C2=A0- was a huge uphill b=
attle that most users just didn't care about. People like passwords. If=
you can find a way to make something that's better than a password but=
just as convenient, fantastic! But I don't think Bitcoin addresses are=
such a thing.</div>
</div></div></div>
--047d7b4142c6d6d10904f638a509--
|
