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
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
|
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 <drak@zikula.org>) id 1VhUYA-0004VG-I1
for bitcoin-development@lists.sourceforge.net;
Sat, 16 Nov 2013 01:19:50 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of zikula.org
designates 209.85.212.181 as permitted sender)
client-ip=209.85.212.181; envelope-from=drak@zikula.org;
helo=mail-wi0-f181.google.com;
Received: from mail-wi0-f181.google.com ([209.85.212.181])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VhUY8-0008RS-Hp
for bitcoin-development@lists.sourceforge.net;
Sat, 16 Nov 2013 01:19:50 +0000
Received: by mail-wi0-f181.google.com with SMTP id f4so1759473wiw.8
for <bitcoin-development@lists.sourceforge.net>;
Fri, 15 Nov 2013 17:19:42 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-type;
bh=EDOYkY6nKOsjEKTPnHQw5hyshz6m3Qn1oZUuDt0Sm6Q=;
b=OnS2j44/8EXpXcHx+jZhP2++BBiCRrKJimILZCXJWqJw/syAzmGUjfMhR4Fnd2P7Ge
PRFsE8wqaLlqD3SGcrY/C5cKI3gn6pa6wO+UBV+KhSbRAPm5F6VgoL0aAANuDJdLJPbN
sHKpaSca7uP/+xuoQdfYwJWiPkPlLONuepPflNsqxNy3fj7C2YjtrBK9Z8pzI5RjViaR
9KxbGr+PSu1HupnJXCxHGqHbgmKc9ZRaLzylM9zj66Eq+zfJlKrC1gJvnqwIqP5Z7lzW
9IULrauoExPylXizIHfw5+wt0eHQNoFFpPh3GMbXoQOMWBAr9HrlcUycPXUbvpb/Epie
y2ZQ==
X-Gm-Message-State: ALoCoQndY6jzryGkqQjFcssjD6edan0bhM4oc6bD7bXmoqNkCQDd+x05yyRi3d/JHkTElwV9H0Pp
X-Received: by 10.180.198.5 with SMTP id iy5mr9135849wic.45.1384564782281;
Fri, 15 Nov 2013 17:19:42 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.93.105 with HTTP; Fri, 15 Nov 2013 17:19:22 -0800 (PST)
In-Reply-To: <201311160110.42132.luke@dashjr.org>
References: <CAKaEYhK4oXH3hB7uS3=AEkA6r0VB5OYyTua+LOP18rq+rYajHg@mail.gmail.com>
<201311142301.39550.luke@dashjr.org>
<CANAnSg1-uW+g3KYyqdfqdvcUybpu2Mn2-j4hJN-5-gVWPrdgvg@mail.gmail.com>
<201311160110.42132.luke@dashjr.org>
From: Drak <drak@zikula.org>
Date: Sat, 16 Nov 2013 01:19:22 +0000
Message-ID: <CANAnSg23FeqWmGRaSNvTp4Y9nAM+t8ttuxs8+HRXH0iJ2sFbjg@mail.gmail.com>
To: Luke-Jr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary=047d7b624e2a045e0a04eb411ce3
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: dashjr.org]
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1VhUY8-0008RS-Hp
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] moving the default display to mbtc
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, 16 Nov 2013 01:19:50 -0000
--047d7b624e2a045e0a04eb411ce3
Content-Type: text/plain; charset=UTF-8
On 16 November 2013 01:10, Luke-Jr <luke@dashjr.org> wrote:
> On Saturday, November 16, 2013 12:41:56 AM Drak wrote:
> > So "a payment clears after one confirmation, but you might want to wait
> > until the payment has been confirmed n times".
> > Then at least you are not using the same word for two different meanings
> > and you're using stuff more familiar in popular lexicon.
> > I dont think it's helpful for users if we use the word "blocks".
>
> "Confirmations" in a numeric context isn't correct, though. We're using to
> it
> because we've been using Bitcoin so long, but to the average person they
> would
> expect it to mean something more than it is. If not referring to blocks,
> then
> perhaps "witnessed N times"?
If you are talking about user interface, I don't think you have to be
technically correct. It must make sense to the user.
A user cares about his balance, and did a payment "go through", and "did my
payment arrive/clear".
The UI is for their benefit.
> > For years, people had a problem with "email address", instead using
> "email
> > number" but they got there eventually. Most people nowadays use "email
> > address"
> > So "payment address" or "bitcoin address" make better sense here when
> > qualified as a "<foo> address" and not just an "address"
> >
> > You could also call it "payment id", but I dont think "invoice id" since
> > no-one pays to an invoice id that's just a reference for a payment, not
> the
> > destination.
> >
> > People are very familiar with Paypal these days, and are familiar with
> > "paypal address" or their "paypal id" so again I think valid contenders
> are
> > "bitcoin address" or "bitcoin id".
>
> I think you might be demonstrating my point with regard to user confusion
> here. Bitcoin addresses are *not* like email addresses, paypal ids, etc.
> Bitcoin addresses aren't the destination - they're point to a destination
> (an
> account in a wallet), but they also represent information such as who is
> paying and what for - in other words, a specific invoice.
Maybe, but again from the user's perspective they pay someone, and they
receive money - just like you do with paypal using an email address.
The technical bits in the middle dont matter to the user and trying to crap
stuff in to be technically correct is just confusing to them.
The UI needs to be about the user and fit with his experience of the world.
Drak
--047d7b624e2a045e0a04eb411ce3
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">On 1=
6 November 2013 01:10, Luke-Jr <span dir=3D"ltr"><<a href=3D"mailto:luke=
@dashjr.org" target=3D"_blank">luke@dashjr.org</a>></span> wrote:<br><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">
<div class=3D"im">On Saturday, November 16, 2013 12:41:56 AM Drak wrote:<br=
>
> So "a payment clears after one confirmation, but you might want t=
o wait<br>
> until the payment has been confirmed n times".<br>
> Then at least you are not using the same word for two different meanin=
gs<br>
> and you're using stuff more familiar in popular lexicon.<br>
> I dont think it's helpful for users if we use the word "block=
s".<br>
<br>
</div>"Confirmations" in a numeric context isn't correct, tho=
ugh. We're using to it<br>
because we've been using Bitcoin so long, but to the average person the=
y would<br>
expect it to mean something more than it is. If not referring to blocks, th=
en<br>
perhaps "witnessed N times"?</blockquote><div><br></div><div>If y=
ou are talking about user interface, I don't think you have to be techn=
ically correct. It must make sense to the user.</div><div>A user cares abou=
t his balance, and did a payment "go through", and "did my p=
ayment arrive/clear".</div>
<div><br></div><div>The UI is for their benefit.</div><div>=C2=A0</div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div class=3D"im">
> For years, people had a problem with =C2=A0"email address", =
instead using "email<br>
> number" but they got there eventually. Most people nowadays use &=
quot;email<br>
> address"<br>
> So "payment address" or "bitcoin address" make bet=
ter sense here when<br>
> qualified as a "<foo> address" and not just an "a=
ddress"<br>
><br>
> You could also call it "payment id", but I dont think "=
invoice id" since<br>
> no-one pays to an invoice id that's just a reference for a payment=
, not the<br>
> destination.<br>
><br>
> People are very familiar with Paypal these days, and are familiar with=
<br>
> "paypal address" or their "paypal id" so again I t=
hink valid contenders are<br>
> "bitcoin address" or "bitcoin id".<br>
<br>
</div>I think you might be demonstrating my point with regard to user confu=
sion<br>
here. Bitcoin addresses are *not* like email addresses, paypal ids, etc.<br=
>
Bitcoin addresses aren't the destination - they're point to a desti=
nation (an<br>
account in a wallet), but they also represent information such as who is<br=
>
paying and what for - in other words, a specific invoice.</blockquote><div>=
<br></div><div>Maybe, but again from the user's perspective they pay so=
meone, and they receive money - just like you do with paypal using an email=
address.</div>
<div>The technical bits in the middle dont matter to the user and trying to=
crap stuff in to be technically correct is just confusing to them.</div><d=
iv><br></div><div>The UI needs to be about the user and fit with his experi=
ence of the world.</div>
<div><br></div><div>Drak</div></div></div></div>
--047d7b624e2a045e0a04eb411ce3--
|
