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
160
161
162
163
164
165
166
|
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 <laanwj@gmail.com>) id 1RaQ2e-0003CQ-IC
for bitcoin-development@lists.sourceforge.net;
Tue, 13 Dec 2011 10:57:00 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.210.47 as permitted sender)
client-ip=209.85.210.47; envelope-from=laanwj@gmail.com;
helo=mail-pz0-f47.google.com;
Received: from mail-pz0-f47.google.com ([209.85.210.47])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1RaQ2d-0004Bj-IW
for bitcoin-development@lists.sourceforge.net;
Tue, 13 Dec 2011 10:57:00 +0000
Received: by dake40 with SMTP id e40so8097563dak.34
for <bitcoin-development@lists.sourceforge.net>;
Tue, 13 Dec 2011 02:56:53 -0800 (PST)
MIME-Version: 1.0
Received: by 10.68.191.103 with SMTP id gx7mr21475188pbc.126.1323773812220;
Tue, 13 Dec 2011 02:56:52 -0800 (PST)
Received: by 10.142.161.12 with HTTP; Tue, 13 Dec 2011 02:56:52 -0800 (PST)
In-Reply-To: <CANEZrP2GvBg19LMyDG_DJe18cvUg3xG7H9S7m+8EemkARz7_Tg@mail.gmail.com>
References: <201112061610.41083.luke@dashjr.org>
<201112101316.31666.luke@dashjr.org>
<20111212205559.GA16665@ulyssis.org>
<201112121602.12806.luke@dashjr.org>
<CANEZrP2GvBg19LMyDG_DJe18cvUg3xG7H9S7m+8EemkARz7_Tg@mail.gmail.com>
Date: Tue, 13 Dec 2011 11:56:52 +0100
Message-ID: <CA+s+GJDxJesFGhE8K2DiR_nxfDebEKtDRGWxeVRC7eaZbO9fSw@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=e89a8ff1c38ad724c504b3f71b95
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
(laanwj[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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
0.0 T_FILL_THIS_FORM_SHORT Fill in a short form with personal
information
-0.0 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1RaQ2d-0004Bj-IW
Cc: Pieter Wuille <pieter.wuille@cs.kuleuven.be>,
bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Version bytes "2.0"
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, 13 Dec 2011 10:57:00 -0000
--e89a8ff1c38ad724c504b3f71b95
Content-Type: text/plain; charset=UTF-8
All,
I fully agree with Mike Hearn on this. Like email addresses, bank numbers,
phone numbers, IPv4/v6 addresses and such the bitcoin address is just an
opaque identifier for machines to be able to send each other messages.
Base58 was chosen not for human readability but to make it easy to
copy/paste.
Of course, sometimes for security reasons you may want to check the
addresses manually, but it is not the prime usage scenario. Although fun as
a nerd pasttime, I don't think we should encourage "addresses with meaning"
to normal users.
Indeed better to focus on alternative ways that don't involve typing or
even seeing the addresses.
Copy/paste of HTML content is currently not possible. You *can* already
drag&drop the bitcoin: link to the client. Bluematt has a pull request to
automatically handle bitcoin: URLs when clicked in the browser.
Wladimir
On Tue, Dec 13, 2011 at 11:38 AM, Mike Hearn <mike@plan99.net> wrote:
> Why does anyone care what an address looks like?
>
> If the user is seeing an address, that's a usability fail right there.
> It's common today because AFAIK nobody finished off the URL handling
> support in the main client for browser integration. It'd be a much better
> use of time to finish off that integration and make it easy for people to
> create links containing a bitcoin: URL (like with copy/paste of text/html
> content).
>
> ------------------------------------------------------------------------------
> Systems Optimization Self Assessment
> Improve efficiency and utilization of IT resources. Drive out cost and
> improve service delivery. Take 5 minutes to use this Systems Optimization
> Self Assessment. http://www.accelacomm.com/jaw/sdnl/114/51450054/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--e89a8ff1c38ad724c504b3f71b95
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div>All,</div><div><br></div>I fully agree with Mike Hearn on this. Like e=
mail addresses, bank numbers, phone numbers, IPv4/v6 addresses and such=C2=
=A0the bitcoin address is just an opaque identifier for machines to be able=
to send each other messages.<div>
<br></div><div><div>Base58 was chosen not for human readability but to make=
it easy to copy/paste.</div></div><div><br></div><div>Of course, sometimes=
for security reasons you may want to check the addresses manually, but it =
is not the prime usage scenario. Although fun as a nerd pasttime, I don'=
;t think we should encourage "addresses with meaning" to normal u=
sers.</div>
<div><br></div><div>Indeed better to focus on alternative ways that don'=
;t involve typing or even seeing the addresses.</div><div><br></div><div>Co=
py/paste of HTML content is currently not possible. You *can* already drag&=
amp;drop the bitcoin: link to the client. Bluematt has a pull request to au=
tomatically handle bitcoin: URLs when clicked in the browser.<br>
<div><div><br></div><div>Wladimir<br><br><div class=3D"gmail_quote">On Tue,=
Dec 13, 2011 at 11:38 AM, Mike Hearn <span dir=3D"ltr"><<a href=3D"mail=
to:mike@plan99.net">mike@plan99.net</a>></span> wrote:<br><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">
Why does anyone care what an address looks like?<br><br>If the user is seei=
ng an address, that's a usability fail right there. It's common tod=
ay because AFAIK nobody finished off the =C2=A0URL handling support in the =
main client for browser integration. It'd be a much better use of time =
to finish off that integration and make it easy for people to create links =
containing a bitcoin: URL (like with copy/paste of text/html content).
<br>-----------------------------------------------------------------------=
-------<br>
Systems Optimization Self Assessment<br>
Improve efficiency and utilization of IT resources. Drive out cost and<br>
improve service delivery. Take 5 minutes to use this Systems Optimization<b=
r>
Self Assessment. <a href=3D"http://www.accelacomm.com/jaw/sdnl/114/51450054=
/" target=3D"_blank">http://www.accelacomm.com/jaw/sdnl/114/51450054/</a><b=
r>_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div><br></div></div></div>
--e89a8ff1c38ad724c504b3f71b95--
|
