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
|
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 <etotheipi@gmail.com>) id 1Vh5mu-0007g4-FP
for bitcoin-development@lists.sourceforge.net;
Thu, 14 Nov 2013 22:53:24 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.216.178 as permitted sender)
client-ip=209.85.216.178; envelope-from=etotheipi@gmail.com;
helo=mail-qc0-f178.google.com;
Received: from mail-qc0-f178.google.com ([209.85.216.178])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Vh5ms-00021y-Lr
for bitcoin-development@lists.sourceforge.net;
Thu, 14 Nov 2013 22:53:24 +0000
Received: by mail-qc0-f178.google.com with SMTP id i7so1655156qcq.9
for <bitcoin-development@lists.sourceforge.net>;
Thu, 14 Nov 2013 14:53:17 -0800 (PST)
X-Received: by 10.224.25.8 with SMTP id x8mr5951961qab.77.1384469597170;
Thu, 14 Nov 2013 14:53:17 -0800 (PST)
Received: from [192.168.1.85] (c-76-111-96-126.hsd1.md.comcast.net.
[76.111.96.126])
by mx.google.com with ESMTPSA id b9sm152403qas.7.2013.11.14.14.53.16
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Thu, 14 Nov 2013 14:53:16 -0800 (PST)
Message-ID: <5285545C.4030607@gmail.com>
Date: Thu, 14 Nov 2013 17:53:16 -0500
From: Alan Reiner <etotheipi@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <CAKaEYhK4oXH3hB7uS3=AEkA6r0VB5OYyTua+LOP18rq+rYajHg@mail.gmail.com> <52852C2D.9020103@gmail.com> <52853D8A.6010501@monetize.io> <CAJHLa0M6CkoDbD6FFixf9-mmhug7DvehSWCJ+EHWVxUDuwNiBg@mail.gmail.com>
<52854F59.9000500@monetize.io>
In-Reply-To: <52854F59.9000500@monetize.io>
X-Enigmail-Version: 1.6
Content-Type: multipart/alternative;
boundary="------------060602010704010707010308"
X-Spam-Score: -0.6 (/)
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: doubleclick.net]
-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
(etotheipi[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
X-Headers-End: 1Vh5ms-00021y-Lr
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, 14 Nov 2013 22:53:24 -0000
This is a multi-part message in MIME format.
--------------060602010704010707010308
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
I really like the XBT idea. It makes a lot of sense to match the ISO
currency symbol (though the ISO guys will have to adjust the way they've
defined the "XBT"). And I do agree that going right to uBTC and
skipping mBTC makes sense, too.
I'd prefer them not be called "micro bitcoins." I really want to call
them "microbes" ... but I'm not sure that has the right flavor for money
transfer :) "Please give me 872 microbes". Perhaps we just call them
"bits." Or even "micros" or "microbits". As I write this, I realize
there's probably 872 threads on the forums about this already...
But we would want to promote a consistent term, to avoid further
confusion when people use different names for the new unit. It's not
guaranteed to be successful, but if we pick a good name, and build it
into the interface on the first release pushing the new unit, we have a
chance to make the transition even easier.
On 11/14/2013 05:31 PM, Mark Friedenbach wrote:
> Whoops, this was meant for the list:
>
> Drawing on analogues from national currencies, it's also possible to
> alleviate the confusion by switching currency symbols, e.g. to XBT or
> NBC (New Bitcoin).
>
> 1 XBC == 1 uBTC
>
> On 11/14/13 2:03 PM, Jeff Garzik wrote:
> > Go straight to uBTC. Humans and existing computer systems handle
> > numbers to the left of the decimals just fine (HK Dollars, Yen).
> > The opposite is untrue (QuickBooks really does not like 3+ decimal
> > places).
>
> > - Jeff
>
> > On Nov 14, 2013 4:40 PM, "Mark Friedenbach" <mark@monetize.io
> > <mailto:mark@monetize.io>> wrote:
>
> > For this reason I'm in favor of skipping mBTC and moving straight
> > to uBTC. Having eight, or even five decimal places is not intuitive
> > to the average user. Two decimal places is becoming standard for
> > new national currencies, and we wouldn't be too far from human
> > scale everyday numbers: 25.00uBTC ~= $0.01 currently. And I don't
> > think very many people on this list would consider bitcoin
> > overvalued in the long term perspective.
>
> > Better to go through a confusing renumbering only once.
>
> > Mark
>
>
------------------------------------------------------------------------------
> DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
> OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
> Free app hosting. Or install the open source package on any LAMP server.
> Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
>
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
--------------060602010704010707010308
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I really like the XBT idea. It makes a lot of sense to match the
ISO currency symbol (though the ISO guys will have to adjust the way
they've defined the "XBT"). And I do agree that going right to uBTC
and skipping mBTC makes sense, too.<br>
<br>
I'd prefer them not be called "micro bitcoins." I really want to
call them "microbes" ... but I'm not sure that has the right flavor
for money transfer :) "Please give me 872 microbes". Perhaps we
just call them "bits." Or even "micros" or "microbits". As I write
this, I realize there's probably 872 threads on the forums about
this already...<br>
<br>
But we would want to promote a consistent term, to avoid further
confusion when people use different names for the new unit. It's
not guaranteed to be successful, but if we pick a good name, and
build it into the interface on the first release pushing the new
unit, we have a chance to make the transition even easier.<br>
<br>
<br>
<br>
<br>
<br>
On 11/14/2013 05:31 PM, Mark Friedenbach wrote:<br>
<blockquote type="cite">Whoops, this was meant for the list:<br>
<br>
Drawing on analogues from national currencies, it's also possible
to<br>
alleviate the confusion by switching currency symbols, e.g. to XBT
or<br>
NBC (New Bitcoin).<br>
<br>
1 XBC == 1 uBTC<br>
<br>
On 11/14/13 2:03 PM, Jeff Garzik wrote:<br>
> Go straight to uBTC. Humans and existing computer systems
handle<br>
> numbers to the left of the decimals just fine (HK Dollars,
Yen).<br>
> The opposite is untrue (QuickBooks really does not like 3+
decimal<br>
> places).<br>
<br>
> - Jeff<br>
<br>
> On Nov 14, 2013 4:40 PM, "Mark Friedenbach"
<<a class="moz-txt-link-abbreviated" href="mailto:mark@monetize.io">mark@monetize.io</a> <br>
> <a class="moz-txt-link-rfc2396E" href="mailto:mark@monetize.io"><mailto:mark@monetize.io></a>> wrote:<br>
<br>
> For this reason I'm in favor of skipping mBTC and moving
straight<br>
> to uBTC. Having eight, or even five decimal places is not
intuitive<br>
> to the average user. Two decimal places is becoming standard
for<br>
> new national currencies, and we wouldn't be too far from
human<br>
> scale everyday numbers: 25.00uBTC ~= $0.01 currently. And I
don't<br>
> think very many people on this list would consider bitcoin<br>
> overvalued in the long term perspective.<br>
<br>
> Better to go through a confusing renumbering only once.<br>
<br>
> Mark<br>
</blockquote>
<span style="white-space: pre;">><br>
>
------------------------------------------------------------------------------<br>
> DreamFactory - Open Source REST & JSON Services for HTML5
& Native Apps<br>
> OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External
API Access<br>
> Free app hosting. Or install the open source package on any
LAMP server.<br>
> Sign up and see examples for AngularJS, jQuery, Sencha Touch
and Native!<br>
>
<a class="moz-txt-link-freetext" href="http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk">http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk</a><br>
> _______________________________________________<br>
> Bitcoin-development mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a><br>
>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a></span><br>
<br>
<br>
</body>
</html>
--------------060602010704010707010308--
|
