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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1WO9C1-0005ub-Mf
for bitcoin-development@lists.sourceforge.net;
Thu, 13 Mar 2014 17:13:17 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.41 as permitted sender)
client-ip=209.85.219.41; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f41.google.com;
Received: from mail-oa0-f41.google.com ([209.85.219.41])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WO9C0-0001SM-Qg
for bitcoin-development@lists.sourceforge.net;
Thu, 13 Mar 2014 17:13:17 +0000
Received: by mail-oa0-f41.google.com with SMTP id j17so1392880oag.0
for <bitcoin-development@lists.sourceforge.net>;
Thu, 13 Mar 2014 10:13:11 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.213.166 with SMTP id nt6mr2401047obc.53.1394730791497;
Thu, 13 Mar 2014 10:13:11 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.71.231 with HTTP; Thu, 13 Mar 2014 10:13:11 -0700 (PDT)
In-Reply-To: <CAJfRnm5Q-XvPLBh1iznXZNT+b=wTkhcPoExVUgK8=oL58ahRkQ@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>
<CAJfRnm5Q-XvPLBh1iznXZNT+b=wTkhcPoExVUgK8=oL58ahRkQ@mail.gmail.com>
Date: Thu, 13 Mar 2014 18:13:11 +0100
X-Google-Sender-Auth: huqUZIa7Mt8Hb9Ieu6jkCfdXMvg
Message-ID: <CANEZrP3dcWOJGyjNkvjPXAPM16NvG8v80JLUa9N5eTWjSbhkFQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Allen Piscitello <allen.piscitello@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c2e60a62791604f480112c
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: 1WO9C0-0001SM-Qg
Cc: Bitcoin Development <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: Thu, 13 Mar 2014 17:13:17 -0000
--001a11c2e60a62791604f480112c
Content-Type: text/plain; charset=UTF-8
>
> Even if a cup of coffee costs 3.12345 mBTC, that's a lot more annoying
> than 3123.45 uBTC.
>
This is subjective though. To me the first price looks like the price of a
cup of coffee (or I just mentally double it). The second looks like the
price of an expensive holiday.
If users really find this so terrible, merchants have a simple solution: do
the rounding before presenting the price. Then the price looks like "3.12
mBTC" which is sort of what I'd expect it to look like. But some wallets
already make digits >2dp smaller so visually you can get precision whilst
still looking similar to what you might expect (this is what Bitcoin Wallet
does).
> I haven't seen a single good argument for keeping it in mBTC (other than
> some people already did it).
>
That's the good argument!
--001a11c2e60a62791604f480112c
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">Even if a cup of coffee costs 3=
.12345 mBTC, that's a lot more annoying than 3123.45 uBTC.</div>
</blockquote><div><br></div><div>This is subjective though. To me the first=
price looks like the price of a cup of coffee (or I just mentally double i=
t). The second looks like the price of an expensive holiday.</div><div>
<br></div><div>If users really find this so terrible, merchants have a simp=
le solution: do the rounding before presenting the price. Then the price lo=
oks like "3.12 mBTC" which is sort of what I'd expect it to l=
ook like. But some wallets already make digits >2dp smaller so visually =
you can get precision whilst still looking similar to what you might expect=
(this is what Bitcoin Wallet does).</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 dir=3D"ltr"><div>I hav=
en't seen a single good argument for keeping it in mBTC (other than som=
e people already did it).</div>
</div></blockquote><div><br></div><div>That's the good argument!</div><=
/div></div></div>
--001a11c2e60a62791604f480112c--
|
