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
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
|
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 <allen.piscitello@gmail.com>) id 1WO8vO-0002Pd-4d
for bitcoin-development@lists.sourceforge.net;
Thu, 13 Mar 2014 16:56:06 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.51 as permitted sender)
client-ip=74.125.82.51; envelope-from=allen.piscitello@gmail.com;
helo=mail-wg0-f51.google.com;
Received: from mail-wg0-f51.google.com ([74.125.82.51])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WO8vM-0007SE-Jd
for bitcoin-development@lists.sourceforge.net;
Thu, 13 Mar 2014 16:56:06 +0000
Received: by mail-wg0-f51.google.com with SMTP id k14so1127929wgh.22
for <bitcoin-development@lists.sourceforge.net>;
Thu, 13 Mar 2014 09:55:58 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.97.72 with SMTP id dy8mr2427424wib.5.1394729758400; Thu,
13 Mar 2014 09:55:58 -0700 (PDT)
Received: by 10.194.76.135 with HTTP; Thu, 13 Mar 2014 09:55:58 -0700 (PDT)
In-Reply-To: <CAKaEYh+Z4J7_xm2+RueV9DCy+MCPmjbkmAYVUjRHEhNa4jf9QQ@mail.gmail.com>
References: <CAKaEYhK4oXH3hB7uS3=AEkA6r0VB5OYyTua+LOP18rq+rYajHg@mail.gmail.com>
<52852C2D.9020103@gmail.com> <52853D8A.6010501@monetize.io>
<CAJHLa0M6CkoDbD6FFixf9-mmhug7DvehSWCJ+EHWVxUDuwNiBg@mail.gmail.com>
<EE02A310-8604-4811-B2D0-FC32C72C20F3@grabhive.com>
<CAJHLa0OMcTCgGESi-F4jT2NA3FyCeMYbD_52j47t3keEYBfK8g@mail.gmail.com>
<CA+s+GJBSGPBQWWYR1NYSc2E4Y1BWAn8zf7xsu4wQ1O8cA8OWbw@mail.gmail.com>
<CAJHLa0NEEppHg_Lmi_Oxnz_gPSHZPfQpeg+-8MrvFYDmdM83-g@mail.gmail.com>
<CANEZrP2O4hDBiCNvO1oV5X7OtnQ4xVDD=RtozQY8ESRHgXQu9w@mail.gmail.com>
<CAJHLa0PB-V+KgEr5uCj+mceESggp8G4MmLGHHpz2UD_R_w-zfQ@mail.gmail.com>
<CANEZrP1sJKGP5A82HbUU+v3oTsc5=U5Gq4Z5TrJ4=2FXLZq4yQ@mail.gmail.com>
<CAKaEYh+Z4J7_xm2+RueV9DCy+MCPmjbkmAYVUjRHEhNa4jf9QQ@mail.gmail.com>
Date: Thu, 13 Mar 2014 11:55:58 -0500
Message-ID: <CAJfRnm5Q-XvPLBh1iznXZNT+b=wTkhcPoExVUgK8=oL58ahRkQ@mail.gmail.com>
From: Allen Piscitello <allen.piscitello@gmail.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=f46d04430670cea78b04f47fd3d9
X-Spam-Score: 1.9 (+)
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
(allen.piscitello[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
2.5 US_DOLLARS_3 BODY: Mentions millions of $ ($NN, NNN,
NNN.NN)
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 LOTS_OF_MONEY Huge... sums of money
X-Headers-End: 1WO8vM-0007SE-Jd
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: Thu, 13 Mar 2014 16:56:06 -0000
--f46d04430670cea78b04f47fd3d9
Content-Type: text/plain; charset=ISO-8859-1
Mike is making an assumption that is not necessary, which is the price of
the most commonly used unit should be between is $.50 and $1000. The issue
to revisit or not shouldn't require $1,000,000 Bitcoin price. Typing a ton
of decimals is incredibly annoying. Doing the mental math in my head is
annoying. Even if a cup of coffee costs 3.12345 mBTC, that's a lot more
annoying than 3123.45 uBTC.
The points that people liked mBTC better than BTC doesn't mean anything
when comparing uBTC to mBTC. Many people just stopped thinking at the mBTC
level, do not understand the implications involved in switching to uBTC, or
even considered uBTC. The idea that we can just poll what people want to
give them the ideal experience is also flawed, in that users often don't
know what they want until they have it in front of them.
There is basically no downside to uBTC, except a few places already
switched to mBTC. For exchanges, which are dealing with decimals since
they will do BTC/USD rather than the opposite, it might make sense for them
to continue to use mBTC or BTC. For wallets and prices for users,
especially when there are large decimals since the price is still based on
more stable currencies, then converted to Bitcoin, let's switch to what is
easiest.
I haven't seen a single good argument for keeping it in mBTC (other than
some people already did it). On the other hand, I've seen numerous great
reasons for switching to uBTC.
My two cents.
On Thu, Mar 13, 2014 at 11:39 AM, Melvin Carvalho
<melvincarvalho@gmail.com>wrote:
>
>
>
> On 13 March 2014 16:50, Mike Hearn <mike@plan99.net> wrote:
>
>> On Thu, Mar 13, 2014 at 3:32 PM, Jeff Garzik <jgarzik@bitpay.com> wrote:
>>
>>> Such hand-wavy, data-free logic is precisely why community
>>> coordination is preferred to random apps making random decisions in
>>> this manner.
>>>
>>
>> That ship sailed months ago. If you wanted a big push for uBTC, then
>> would have been the time. Though given that it'd have made lots of normal
>> balances incredibly huge, perhaps it's a good thing that didn't happen.
>> Also "milli" is a unit people encounter in daily life whereas micro isn't.
>> Is it milli / micro / nano or milli / nano / micro? I bet a lot of people
>> would get that wrong.
>>
>> If you have to export to financial packages that can't handle fractional
>> pennies, then by all means represent prices in whatever units you like for
>> that purpose, but in software designed for ordinary people in everyday life
>> mBTC is a pretty good fit.
>>
>> Besides, fractional pennies crop up in existing currencies too (the
>> famous Verizon Math episode showed this), so if a financial package insists
>> on rounding to 2dp then I guess it may sometimes do the wrong thing in some
>> business cases already.
>>
>> Fundamentally, more than two decimal places tends to violate the
>>> Principle Of Least Astonishment with many humans, and as a result,
>>> popular software systems have been written with that assumption.
>>
>>
>> Lots of people use currencies that don't have any fractional components
>> at all ! So perhaps all prices should be denominated in satoshis to ensure
>> that they're not surprised :)
>>
>> The (number) line has to be drawn somewhere. Wallets are free to suppress
>> more than 2dp of precision and actually Andreas' app lets you choose your
>> preferred precision. So I think in the end it won't matter a whole lot, if
>> the defaults end up being wrong people can change them until wallet authors
>> catch up.
>>
>
> +1 agree with Mike on everything
>
> A couple of points:
>
> 1. bitcoinity already switched to mbtc aka millitbits (
> https://en.bitcoin.it/wiki/MilliBit ) and it was positively recieved,
> they got quite a few donations
>
> 2. If you watch Gavin's talk at the CFR he suggests the community comes to
> a consensus through implementations rather than top down decision making
> (If I understood correctly)
>
> I think it's up to wallet maintainers whether to switch the default.
>
>
>
>>
>>
>> ------------------------------------------------------------------------------
>> Learn Graph Databases - Download FREE O'Reilly Book
>> "Graph Databases" is the definitive new guide to graph databases and their
>> applications. Written by three acclaimed leaders in the field,
>> this first edition is now available. Download your free book today!
>> http://p.sf.net/sfu/13534_NeoTech
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>>
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--f46d04430670cea78b04f47fd3d9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Mike is making an assumption that is not necessary, which =
is the price of the most commonly used unit should be between is $.50 and $=
1000. =A0The issue to revisit or not shouldn't require $1,000,000 Bitco=
in price. =A0Typing a ton of decimals is incredibly annoying. =A0Doing the =
mental math in my head is annoying. =A0Even if a cup of coffee costs 3.1234=
5 mBTC, that's a lot more annoying than 3123.45 uBTC.<div>
<br></div><div>The points that people liked mBTC better than BTC doesn'=
t mean anything when comparing uBTC to mBTC. =A0Many people just stopped th=
inking at the mBTC level, do not understand the implications involved in sw=
itching to uBTC, or even considered uBTC. =A0The idea that we can just poll=
what people want to give them the ideal experience is also flawed, in that=
users often don't know what they want until they have it in front of t=
hem.</div>
<div><br></div><div>There is basically no downside to uBTC, except a few pl=
aces already switched to mBTC. =A0For exchanges, which are dealing with dec=
imals since they will do BTC/USD rather than the opposite, it might make se=
nse for them to continue to use mBTC or BTC. =A0For wallets and prices for =
users, especially when there are large decimals since the price is still ba=
sed on more stable currencies, then converted to Bitcoin, let's switch =
to what is easiest.</div>
<div><br></div><div>I haven't seen a single good argument for keeping i=
t in mBTC (other than some people already did it). =A0On the other hand, I&=
#39;ve seen numerous great reasons for switching to uBTC.</div><div><br></d=
iv>
<div>My two cents.</div></div><div class=3D"gmail_extra"><br><br><div class=
=3D"gmail_quote">On Thu, Mar 13, 2014 at 11:39 AM, Melvin Carvalho <span di=
r=3D"ltr"><<a href=3D"mailto:melvincarvalho@gmail.com" target=3D"_blank"=
>melvincarvalho@gmail.com</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><br><div class=3D"gmail_ext=
ra"><br><br><div class=3D"gmail_quote"><div><div class=3D"h5">On 13 March 2=
014 16:50, Mike Hearn <span dir=3D"ltr"><<a href=3D"mailto:mike@plan99.n=
et" target=3D"_blank">mike@plan99.net</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div cla=
ss=3D"gmail_extra"><div class=3D"gmail_quote"><div>On Thu, Mar 13, 2014 at =
3:32 PM, Jeff Garzik <span dir=3D"ltr"><<a href=3D"mailto:jgarzik@bitpay=
.com" target=3D"_blank">jgarzik@bitpay.com</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div>Such hand-wavy, data=
-free logic is precisely why community<br></div>
coordination is preferred to random apps making random decisions in<br>
this manner.<br></blockquote><div><br></div></div><div>That ship sailed mon=
ths ago. If you wanted a big push for uBTC, then would have been the time. =
Though given that it'd have made lots of normal balances incredibly hug=
e, perhaps it's a good thing that didn't happen. Also "milli&q=
uot; is a unit people encounter in daily life whereas micro isn't. Is i=
t milli / micro / nano or milli / nano / micro? I bet a lot of people would=
get that wrong.</div>
<div><br></div><div>If you have to export to financial packages that can=
9;t handle fractional pennies, then by all means represent prices in whatev=
er units you like for that purpose, but in software designed for ordinary p=
eople in everyday life mBTC is a pretty good fit.</div>
<div>=A0</div><div>Besides, fractional pennies crop up in existing currenci=
es too (the famous Verizon Math episode showed this), so if a financial pac=
kage insists on rounding to 2dp then I guess it may sometimes do the wrong =
thing in some business cases already.</div>
<div>
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Fundamenta=
lly, more than two decimal places tends to violate the<br>
Principle Of Least Astonishment with many humans, and as a result,<br>
popular software systems have been written with that assumption.</blockquot=
e><div><br></div></div><div>Lots of people use currencies that don't ha=
ve any fractional components at all ! So perhaps all prices should be denom=
inated in satoshis to ensure that they're not surprised :)</div>
<div><br></div><div>The (number) line has to be drawn somewhere. Wallets ar=
e free to suppress more than 2dp of precision and actually Andreas' app=
lets you choose your preferred precision. So I think in the end it won'=
;t matter a whole lot, if the defaults end up being wrong people can change=
them until wallet authors catch up.</div>
</div></div></div></blockquote><div><br></div></div></div><div>+1 agree wit=
h Mike on everything<br><br></div><div>A couple of points:<br><br></div><di=
v>1. bitcoinity already switched to mbtc aka millitbits ( <a href=3D"https:=
//en.bitcoin.it/wiki/MilliBit" target=3D"_blank">https://en.bitcoin.it/wiki=
/MilliBit</a> ) and it was positively recieved, they got quite a few donati=
ons<br>
</div><div><br></div><div>2. If you watch Gavin's talk at the CFR he su=
ggests the community comes to a consensus through implementations rather th=
an top down decision making (If I understood correctly)<br><br></div><div>
I think it's up to wallet maintainers whether to switch the default.=A0=
<br></div><div class=3D""><div><br></div><div>=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">
</div></div></div>
<br>-----------------------------------------------------------------------=
-------<br>
Learn Graph Databases - Download FREE O'Reilly Book<br>
"Graph Databases" is the definitive new guide to graph databases =
and their<br>
applications. Written by three acclaimed leaders in the field,<br>
this first edition is now available. Download your free book today!<br>
<a href=3D"http://p.sf.net/sfu/13534_NeoTech" target=3D"_blank">http://p.sf=
.net/sfu/13534_NeoTech</a><br>_____________________________________________=
__<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net" target=3D"_bla=
nk">Bitcoin-development@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></div><br></div></div>
<br>-----------------------------------------------------------------------=
-------<br>
Learn Graph Databases - Download FREE O'Reilly Book<br>
"Graph Databases" is the definitive new guide to graph databases =
and their<br>
applications. Written by three acclaimed leaders in the field,<br>
this first edition is now available. Download your free book today!<br>
<a href=3D"http://p.sf.net/sfu/13534_NeoTech" target=3D"_blank">http://p.sf=
.net/sfu/13534_NeoTech</a><br>_____________________________________________=
__<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>
--f46d04430670cea78b04f47fd3d9--
|