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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
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 1RaQCn-0007CX-9S
for bitcoin-development@lists.sourceforge.net;
Tue, 13 Dec 2011 11:07:29 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.53 as permitted sender)
client-ip=74.125.82.53; envelope-from=mh.in.england@gmail.com;
helo=mail-ww0-f53.google.com;
Received: from mail-ww0-f53.google.com ([74.125.82.53])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
(Exim 4.76) id 1RaQCh-0005fC-R7
for bitcoin-development@lists.sourceforge.net;
Tue, 13 Dec 2011 11:07:29 +0000
Received: by wgbds1 with SMTP id ds1so12480333wgb.10
for <bitcoin-development@lists.sourceforge.net>;
Tue, 13 Dec 2011 03:07:17 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.133.224 with SMTP id q74mr41332wei.56.1323774437691; Tue,
13 Dec 2011 03:07:17 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.216.8.7 with HTTP; Tue, 13 Dec 2011 03:07:17 -0800 (PST)
In-Reply-To: <CA+s+GJDxJesFGhE8K2DiR_nxfDebEKtDRGWxeVRC7eaZbO9fSw@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>
<CA+s+GJDxJesFGhE8K2DiR_nxfDebEKtDRGWxeVRC7eaZbO9fSw@mail.gmail.com>
Date: Tue, 13 Dec 2011 12:07:17 +0100
X-Google-Sender-Auth: JPjrk9IslccmJRRX6jQFxDhiWN8
Message-ID: <CANEZrP3EpkCaK2nXXazX-D-a0yO_3SkWXg74V2zh+nCM=Ko20w@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Wladimir <laanwj@gmail.com>
Content-Type: multipart/alternative; boundary=0016e6dee8271f0fed04b3f7416f
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: 1RaQCh-0005fC-R7
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 11:07:29 -0000
--0016e6dee8271f0fed04b3f7416f
Content-Type: text/plain; charset=UTF-8
>
> Base58 was chosen not for human readability but to make it easy to
> copy/paste.
>
It was also chosen for hand-writeability, weirdly enough. That's why it
excludes some confusible characters. But Satoshi didn't really understand
how people would end up using Bitcoin, he originally imagined most
transactions being done directly between pairs of IP 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.
>
That's cool. I hope Matts change gets merged soon. Then the issue becomes
how do people find out about this capability? Expecting people to learn how
to hand-craft Bitcoin links won't work. But all modern operating systems
support copy/paste and drag/drop of rich content. Qt probably makes it easy
to expose an UI like this:
*Pay me* [Copy to clipboard]
Clicking the link in the UI would pop up an alert saying something like
"You can drag this link to an email, chat window or editing program."
Dragging it/pushing the copy button would just set the drag/clipboard data
as a bit of text/html content. So then you can just copy/paste into an
email or HTML editor. It wouldn't work for forums that use bbCode, though I
guess there's no particular reason the forum software can't turn <a href>
into [url=] automatically.
--0016e6dee8271f0fed04b3f7416f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>Base58 =
was chosen not for human readability but to make it easy to copy/paste.</di=
v></div>
</blockquote><div><br></div><div>It was also chosen for hand-writeability, =
weirdly enough. That's why it excludes some confusible characters. But =
Satoshi didn't really understand how people would end up using Bitcoin,=
he originally imagined most transactions being done directly between pairs=
of IP addresses.</div>
<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div>Copy/paste of HTML con=
tent is currently not possible. You *can* already drag&drop the bitcoin=
: link to the client. Bluematt has a pull request to automatically handle b=
itcoin: URLs when clicked in the browser.</div>
</blockquote><div><br></div><div>That's cool. I hope Matts change gets =
merged soon. Then the issue becomes how do people find out about this capab=
ility? Expecting people to learn how to hand-craft Bitcoin links won't =
work. But all modern operating systems support copy/paste and drag/drop of =
rich content. Qt probably makes it easy to expose an UI like this:</div>
<div><br></div><div>=C2=A0 =C2=A0<u><font class=3D"Apple-style-span" color=
=3D"#3333ff">Pay me</font></u> =C2=A0 =C2=A0[Copy to clipboard]</div><div><=
br></div><div>Clicking the link in the UI would pop up an alert saying some=
thing like</div><div>
<br></div><div>=C2=A0 =C2=A0"You can drag this link to an email, chat =
window or editing program."</div><div><br></div><div>Dragging it/pushi=
ng the copy button would just set the drag/clipboard data as a bit of text/=
html content. So then you can just copy/paste into an email or HTML editor.=
It wouldn't work for forums that use bbCode, though I guess there'=
s no particular reason the forum software can't turn <a href> int=
o [url=3D] automatically.</div>
</div>
--0016e6dee8271f0fed04b3f7416f--
|
