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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <luke@dashjr.org>) id 1Vh63i-00013f-3N
for bitcoin-development@lists.sourceforge.net;
Thu, 14 Nov 2013 23:10:46 +0000
X-ACL-Warn:
Received: from zinan.dashjr.org ([192.3.11.21])
by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1Vh63h-00086h-4a for bitcoin-development@lists.sourceforge.net;
Thu, 14 Nov 2013 23:10:46 +0000
Received: from ishibashi.localnet (unknown
[IPv6:2001:470:5:265:be5f:f4ff:febf:4f76])
(Authenticated sender: luke-jr)
by zinan.dashjr.org (Postfix) with ESMTPSA id 080BE1080833;
Thu, 14 Nov 2013 23:10:45 +0000 (UTC)
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Date: Thu, 14 Nov 2013 23:10:32 +0000
User-Agent: KMail/1.13.7 (Linux/3.12.0; KDE/4.10.5; x86_64; ; )
References: <CAKaEYhK4oXH3hB7uS3=AEkA6r0VB5OYyTua+LOP18rq+rYajHg@mail.gmail.com>
<52854F59.9000500@monetize.io> <5285545C.4030607@gmail.com>
In-Reply-To: <5285545C.4030607@gmail.com>
X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F
X-PGP-Key-ID: BD02942421F4889F
X-PGP-Keyserver: hkp://pgp.mit.edu
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <201311142310.33829.luke@dashjr.org>
X-Spam-Score: -0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
X-Headers-End: 1Vh63h-00086h-4a
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 23:10:46 -0000
On Thursday, November 14, 2013 10:53:16 PM Alan Reiner wrote:
> 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.
As long as we're using SI units, IMO we should stick to SI. That means "micro-
bitcoins". *Informally/spoken*, an abbreviation like "mibicoins" might make
sense.
Luke
|
