summaryrefslogtreecommitdiff
path: root/ee/78c60153cff7748a5640d3791985c9b138636a
blob: 8edaf10281436d23078a10cdfe041194107af71a (plain)
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
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 <mcaldwell@swipeclock.com>) id 1WbwZh-0003DW-8a
	for bitcoin-development@lists.sourceforge.net;
	Sun, 20 Apr 2014 18:34:45 +0000
Received-SPF: fail (sog-mx-1.v43.ch3.sourceforge.com: domain of swipeclock.com
	does not designate 74.201.97.201 as permitted sender)
	client-ip=74.201.97.201; envelope-from=mcaldwell@swipeclock.com;
	helo=mxout.myoutlookonline.com; 
Received: from mxout.myoutlookonline.com ([74.201.97.201])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.76) id 1WbwZd-0005Ta-Tk
	for bitcoin-development@lists.sourceforge.net;
	Sun, 20 Apr 2014 18:34:45 +0000
Received: from mxout.myoutlookonline.com (localhost [127.0.0.1])
	by mxout.myoutlookonline.com (Postfix) with ESMTP id 27F42416864;
	Sun, 20 Apr 2014 14:34:48 -0400 (EDT)
X-Virus-Scanned: by SpamTitan at mail.lan
Received: from HUB027.mail.lan (unknown [10.110.2.1])
	by mxout.myoutlookonline.com (Postfix) with ESMTP id 2A59741683E;
	Sun, 20 Apr 2014 14:34:47 -0400 (EDT)
Received: from MAILR023.mail.lan ([10.110.18.122]) by HUB027.mail.lan
	([10.110.17.27]) with mapi; Sun, 20 Apr 2014 14:33:24 -0400
From: Mike Caldwell <mcaldwell@swipeclock.com>
To: Arne Brutschy <abrutschy@xylon.de>
Date: Sun, 20 Apr 2014 14:34:32 -0400
Thread-Topic: [Bitcoin-development] "bits": Unit of account
Thread-Index: Ac9cxy3HdJBuocmuQWy0ysPbsgqn5A==
Message-ID: <66562DD7-1E46-4F14-BD36-7AA4F1E7D739@swipeclock.com>
References: <CAJKMfeQO6pyi5b-83FyMSHcq0Sa1QkP+RouQVBdCYPtXXboY8A@mail.gmail.com>
	<53540715.7050803@xylon.de>
	<1C408C12-B39B-46E4-B997-153D566158B1@swipeclock.com>
	<53541079.9000909@xylon.de>
In-Reply-To: <53541079.9000909@xylon.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Spam-Score: 4.9 (++++)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	4.0 SPF_CHECK_FAIL SPF reports sender host as NOT permitted to send
	mails from
	0.9 SPF_FAIL SPF: sender does not match SPF record (fail)
X-Headers-End: 1WbwZd-0005Ta-Tk
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] "bits": Unit of account
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: Sun, 20 Apr 2014 18:34:45 -0000

Mainly because it is short, memorable, effectively leads the listener to in=
fer the proper meaning, is culturally neutral, is easy to say by speakers o=
f just about any language, and many other reasons.=20

Mike

Sent from my iPhone

> On Apr 20, 2014, at 12:23 PM, "Arne Brutschy" <abrutschy@xylon.de> wrote:
>=20
> agree that overloading isn't an issue when necessary, but my point was
> that the necessity is lacking. If we're free to pick anything, why pick
> something that is overloaded?
>=20
> Moreover, "bit" is an abbreviation of bitcoin and might be confused with
> it. Most currencies use a work that is phonetically very different and
> short, so why not do the same?
>=20
> Pluk, or cred, or finney (as proposed the thread I posted), or
> whichever. We could call it "unsp" for unspent ;)
>=20
> Arne
>=20