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
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <marek@palatinus.cz>) id 1WgcP3-00078W-IH
for bitcoin-development@lists.sourceforge.net;
Sat, 03 May 2014 16:03:05 +0000
X-ACL-Warn:
Received: from mail-ve0-f170.google.com ([209.85.128.170])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WgcP1-0001H3-Cw
for bitcoin-development@lists.sourceforge.net;
Sat, 03 May 2014 16:03:05 +0000
Received: by mail-ve0-f170.google.com with SMTP id db11so2097236veb.15
for <bitcoin-development@lists.sourceforge.net>;
Sat, 03 May 2014 09:02:57 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:sender:in-reply-to:references:from
:date:message-id:subject:to:cc:content-type;
bh=29DXEyncH2OKlcymvZ8R12lxPxLdj5ebA0epX2hNB8k=;
b=PeKOYY8MBXuqLDUjnlXXwXvDQwCgvYRFGF9u1jX+xmEfj8vZYbr6OqbFOcLRZrq80H
a27c6DgwdHSQG7m6L7e9zWwRSMsYH5MTr72UdTgRMMb/VJTC8GJ34c/8gxfKyrPfq+MR
YpqnrcYEcLeIHJzyG/e9Qqf4brcryA8rumIy0ljEt4D8r5w2467nPSPnNqJhxoDdy8sj
XMnchLdnNIUlGmXZGrMxo3ViYrlIgR/jvl76Fu28rPbYe///6Z1I90BoYex77/CHp5hW
eHBY4DqGdHP3jYfxblVD2bcxR7erLOm7frr4gYJtwc8wV8Vgo53Ar8Ms9luABdfoIkMj
3R1A==
X-Gm-Message-State: ALoCoQk4WcoUwy0BvqreSCoc+cbl3XB+t5qob4ittD0cmK2xuAXCj7TyAwKKQi9pg8pNE0B7D7eL
X-Received: by 10.221.50.70 with SMTP id vd6mr3566vcb.51.1399132977777; Sat,
03 May 2014 09:02:57 -0700 (PDT)
MIME-Version: 1.0
Sender: marek@palatinus.cz
Received: by 10.58.234.68 with HTTP; Sat, 3 May 2014 09:02:27 -0700 (PDT)
In-Reply-To: <CANOOu=9orMZH6fpTfkO8zgwPDmwpA8WW78EKwSTiw2GXn7UCxA@mail.gmail.com>
References: <CACq0ZD6EJnG4iwehfcFU-4AhBiNdtyf7eE9iGW8d6rv6327Eug@mail.gmail.com>
<53644F13.1080203@gmail.com>
<CACq0ZD7s8tp8GvJhEhZx4T7xMpeZ+tz5HNKQK-p=f=R10NaCmA@mail.gmail.com>
<CANOOu=9orMZH6fpTfkO8zgwPDmwpA8WW78EKwSTiw2GXn7UCxA@mail.gmail.com>
From: slush <slush@centrum.cz>
Date: Sat, 3 May 2014 18:02:27 +0200
X-Google-Sender-Auth: P3qtHUEk8OtdhGtCudQit-dcL6I
Message-ID: <CAJna-HiqBG1+iN+gMiM6F_nXCkJZyC78u9rF=hmdPZm_Yb7VJw@mail.gmail.com>
To: Christophe Biocca <christophe.biocca@gmail.com>
Content-Type: multipart/alternative; boundary=001a11339a762262cd04f8810873
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(slush[at]centrum.cz)
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1WgcP1-0001H3-Cw
Cc: Bitcoin Development <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: Sat, 03 May 2014 16:03:05 -0000
--001a11339a762262cd04f8810873
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Excellent points Christophe!
Although moving to 1e-6 units is fine for me and I see advantages of doing
this, I don't get that people on this mailing list are fine with calling
such unit "bit". It's geeky as hell, ambiguous and confusing.
slush
On Sat, May 3, 2014 at 5:48 PM, Christophe Biocca <
christophe.biocca@gmail.com> wrote:
> Context as a disambiguator works fine when the interlocutors
> understand the topics they're talking about.
> Not a day goes by without me seeing "neurotypical people" get horribly
> confused between RAM and Hard Drive sizes, because they share the same
> units (not that that can be helped, as the units are supposed to be
> the same, base 1000 vs 1024 notwithstanding).
>
> Bit (as a unit) is already really confusing for anyone who doesn't
> deal with it on a regular basis. I think people who don't see an issue
> are making an assumption based on their own lack of confusion. We
> understand computer science AND Bitcoin. Most people have zero
> understanding of either.
>
> Bitcoin already has a ton of issues with terrible names for things:
>
> - Mining (for transaction validation).
> - Addresses (which are meant to be one-time use, and don't even really
> exist at the network level).
> - Wallets (which don't hold your bitcoins, can be copied, and all
> backups can be stolen from equally).
>
> I end up having to make the distinctions obvious every time I explain
> Bitcoin to someone new to it. There's an acceptable tradeoff here,
> because there were arguably no better words to assign to these
> concepts (although I'd argue mining is a really awful metaphor, and is
> the one that prompts the most questions from people). Then add to the
> pile a bunch of third parties naming themselves after parts of the
> protocol (Coinbase,Blockchain.info). Not blaming them for it, but I've
> definitiely seen average people get confused between "the blockchain"
> and "blockchain.info" (not so much Coinbase, because that name doesn't
> come up in beginner explanations).
>
> It seems downright masochistic to add
> yet-another-word-that-doesn't-mean-what-you-think-it-means to the pile
> for no reason other than aesthetics. Are we actively trying to confuse
> people?
>
> On Sat, May 3, 2014 at 1:41 AM, Aaron Voisine <voisine@gmail.com> wrote:
> > I have to agree with Mike. Human language is surprisingly tolerant of
> > overloading and inference from context. Neurotypical people have no
> > problem with it and perceive a software engineer's aversion to it as
> > being pedantic and strange. Note that "bits" was a term for a unit of
> > money long before the invention of digital computers.
> >
> > Aaron
> >
> > There's no trick to being a humorist when you have the whole
> > government working for you -- Will Rodgers
> >
> >
> > On Fri, May 2, 2014 at 7:06 PM, Gordon Mohr <gojomo@gmail.com> wrote:
> >> [resend - apologies if duplicate]
> >>
> >> Microbitcoin is a good-sized unit, workable for everyday transaction
> >> values, with room-to-grow, and a nice relationship to satoshis as
> 'cents'.
> >>
> >> But "bits" has problems as a unit name.
> >>
> >> "Bits" will be especially problematic whenever people try to graduate
> >> from informal use to understanding the system internals - that is, whe=
n
> >> the real "bits" of key sizes, hash sizes, and storage/bandwidth needs
> >> become important. The "bit" as "binary digit" was important enough tha=
t
> >> Satoshi named the system after it; that homage gets lost if the word i=
s
> >> muddied with a new retconned meaning that's quite different.
> >>
> >> Some examples of possible problems:
> >>
> >> * If "bit" equals "100 satoshis", then the natural-language unpacking =
of
> >> "bit-coin" is "100 satoshi coin", which runs against all prior usage.
> >>
> >> * If people are informed that a "256-bit private key" is what ultimate=
ly
> >> controls their balances, it could prompt confusion like, "if each key
> >> has 256-bits, will I need 40 keys to hold 10,000.00 bits?"
> >>
> >> * When people learn that there are 8 bits to a byte, they may think,
> >> "OK, my wallet holding my 80,000.00 bits will then take up 10
> kilobytes".
> >>
> >> * When people naturally extend "bit" into "kilobits" to mean "1000
> >> bits", then the new coinage "kilobits" will mean the exact same amount
> >> (100,000 satoshi) as many have already been calling "millibits".
> >>
> >> I believe it'd be best to pick a new made-up single-syllable word as a
> >> synonym for "microbitcoin", and I've laid out the case for "zib" as th=
at
> >> word at <http://zibcoin.org>.
> >>
> >> 'Zib' also lends itself to an expressive unicode symbol, '=C6=B5'
> >> (Z-with-stroke), that remains distinctive even if it loses its stroke =
or
> >> gets case-reversed. (Comparatively, all 'b'-derived symbols for
> >> data-bits, bitcoins, or '100 satoshi bits' risk collision in contexts
> >> where subtleties of casing/stroking are lost.)
> >>
> >> (There's summary of more problems with "bit" in the zibcoin.org FAQ
> at:
> >> <http://zibcoin.org/faq#why-not-bits-to-mean-microbitcoins>.)
> >>
> >> - Gordon
> >>
> >> On 5/1/14, 3:35 PM, Aaron Voisine wrote:
> >>> I'm also a big fan of standardizing on microBTC as the standard unit.
> >>> I didn't like the name "bits" at first, but the more I think about it=
,
> >>> the more I like it. The main thing going for it is the fact that it's
> >>> part of the name bitcoin. If Bitcoin is the protocol and network, bit=
s
> >>> are an obvious choice for the currency unit.
> >>>
> >>> I would like to propose using Unicode character U+0180, lowercase b
> >>> with stroke, as the symbol to represent the microBTC denomination,
> >>> whether we call bits or something else:
> >>> http://www.fileformat.info/info/unicode/char/0180/index.htm
> >>>
> >>> Another candidate is Unicode character U+2422, the blank symbol, but =
I
> >>> prefer stroke b.
> >>> http://www.fileformat.info/info/unicode/char/2422/index.htm
> >>>
> >>> Aaron
> >>>
> >>> There's no trick to being a humorist when you have the whole
> >>> government working for you -- Will Rodgers
> >>>
> >>>> On Apr 21, 2014 5:41 AM, "Pieter Wuille" <pieter.wuille@gm...> wrote=
:
> >>>>
> >>>>> On Apr 21, 2014 3:37 AM, "Un Ix" <slashdevnull@...> wrote:
> >>>>>
> >>>>> Something tells me this would be reduced to a single syllable in
> common
> >>>>> usage I.e. bit.
> >>>>
> >>>> What units will be called colloquially is not something developers
> will
> >>>> determine. It will vary, depend on language and culture, and is not
> >>>> relevant to this discussion in my opinion.
> >>>>
> >>>> It may well be that people in some geographic or language area will
> end up
> >>>> (or for a while) calling 1e-06 BTC "bits". That's fine, but using
> that as
> >>>> "official" name in software would be very strange and potentially
> confusing
> >>>> in my opinion. As mentioned by others, that would seem to me like
> calling
> >>>> dollars "bucks" in bank software. Nobody seems to have a problem wit=
h
> >>>> having colloquial names, but "US dollar" or "euro" are far less
> ambiguous
> >>>> than "bit". I think we need a more distinctive name.
> >>>>
> >>>> --
> >>>> Pieter
> >>>
> >>>
> -------------------------------------------------------------------------=
-----
> >>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FRE=
E
> >>> Instantly run your Selenium tests across 300+ browser/OS combos. Get
> >>> unparalleled scalability from the best Selenium testing platform
> available.
> >>> Simple to use. Nothing to install. Get started now for free."
> >>> http://p.sf.net/sfu/SauceLabs
> >>> _______________________________________________
> >>> Bitcoin-development mailing list
> >>> Bitcoin-development@lists.sourceforge.net
> >>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> >>>
> >>
> >>
> -------------------------------------------------------------------------=
-----
> >> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> >> Instantly run your Selenium tests across 300+ browser/OS combos. Get
> >> unparalleled scalability from the best Selenium testing platform
> available.
> >> Simple to use. Nothing to install. Get started now for free."
> >> http://p.sf.net/sfu/SauceLabs
> >> _______________________________________________
> >> Bitcoin-development mailing list
> >> Bitcoin-development@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> >
> >
> -------------------------------------------------------------------------=
-----
> > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> > Instantly run your Selenium tests across 300+ browser/OS combos. Get
> > unparalleled scalability from the best Selenium testing platform
> available.
> > Simple to use. Nothing to install. Get started now for free."
> > http://p.sf.net/sfu/SauceLabs
> > _______________________________________________
> > Bitcoin-development mailing list
> > Bitcoin-development@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
> -------------------------------------------------------------------------=
-----
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos. Get
> unparalleled scalability from the best Selenium testing platform availabl=
e.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--001a11339a762262cd04f8810873
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Excellent points Christophe!<div><br></div><div>Although m=
oving to 1e-6 units is fine for me and I see advantages of doing this, I do=
n't get that people on this mailing list are fine with calling such uni=
t "bit". It's geeky as hell, ambiguous and confusing.=C2=A0</=
div>
<div><br></div><div>slush</div></div><div class=3D"gmail_extra"><br><br><di=
v class=3D"gmail_quote">On Sat, May 3, 2014 at 5:48 PM, Christophe Biocca <=
span dir=3D"ltr"><<a href=3D"mailto:christophe.biocca@gmail.com" target=
=3D"_blank">christophe.biocca@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">Context as a disambiguator works fine when t=
he interlocutors<br>
understand the topics they're talking about.<br>
Not a day goes by without me seeing "neurotypical people" get hor=
ribly<br>
confused between RAM and Hard Drive sizes, because they share the same<br>
units (not that that can be helped, as the units are supposed to be<br>
the same, base 1000 vs 1024 notwithstanding).<br>
<br>
Bit (as a unit) is already really confusing for anyone who doesn't<br>
deal with it on a regular basis. I think people who don't see an issue<=
br>
are making an assumption based on their own lack of confusion. We<br>
understand computer science AND Bitcoin. Most people have zero<br>
understanding of either.<br>
<br>
Bitcoin already has a ton of issues with terrible names for things:<br>
<br>
- Mining (for transaction validation).<br>
- Addresses (which are meant to be one-time use, and don't even really<=
br>
exist at the network level).<br>
- Wallets (which don't hold your bitcoins, can be copied, and all<br>
backups can be stolen from equally).<br>
<br>
I end up having to make the distinctions obvious every time I explain<br>
Bitcoin to someone new to it. There's an acceptable tradeoff here,<br>
because there were arguably no better words to assign to these<br>
concepts (although I'd argue mining is a really awful metaphor, and is<=
br>
the one that prompts the most questions from people). Then add to the<br>
pile a bunch of third parties naming themselves after parts of the<br>
protocol (Coinbase,Blockchain.info). Not blaming them for it, but I've<=
br>
definitiely seen average people get confused between "the blockchain&q=
uot;<br>
and "<a href=3D"http://blockchain.info" target=3D"_blank">blockchain.i=
nfo</a>" (not so much Coinbase, because that name doesn't<br>
come up in beginner explanations).<br>
<br>
It seems downright masochistic to add<br>
yet-another-word-that-doesn't-mean-what-you-think-it-means to the pile<=
br>
for no reason other than aesthetics. Are we actively trying to confuse<br>
people?<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On Sat, May 3, 2014 at 1:41 AM, Aaron Voisine <<a href=3D"mailto:voisine=
@gmail.com">voisine@gmail.com</a>> wrote:<br>
> I have to agree with Mike. Human language is surprisingly tolerant of<=
br>
> overloading and inference from context. Neurotypical people have no<br=
>
> problem with it and perceive a software engineer's aversion to it =
as<br>
> being pedantic and strange. Note that "bits" was a term for =
a unit of<br>
> money long before the invention of digital computers.<br>
><br>
> Aaron<br>
><br>
> There's no trick to being a humorist when you have the whole<br>
> government working for you -- Will Rodgers<br>
><br>
><br>
> On Fri, May 2, 2014 at 7:06 PM, Gordon Mohr <<a href=3D"mailto:gojo=
mo@gmail.com">gojomo@gmail.com</a>> wrote:<br>
>> [resend - apologies if duplicate]<br>
>><br>
>> Microbitcoin is a good-sized unit, workable for everyday transacti=
on<br>
>> values, with room-to-grow, and a nice relationship to satoshis as =
'cents'.<br>
>><br>
>> But "bits" has problems as a unit name.<br>
>><br>
>> "Bits" will be especially problematic whenever people tr=
y to graduate<br>
>> from informal use to understanding the system internals - that is,=
when<br>
>> the real "bits" of key sizes, hash sizes, and storage/ba=
ndwidth needs<br>
>> become important. The "bit" as "binary digit" =
was important enough that<br>
>> Satoshi named the system after it; that homage gets lost if the wo=
rd is<br>
>> muddied with a new retconned meaning that's quite different.<b=
r>
>><br>
>> Some examples of possible problems:<br>
>><br>
>> * If "bit" equals "100 satoshis", then the nat=
ural-language unpacking of<br>
>> "bit-coin" is "100 satoshi coin", which runs a=
gainst all prior usage.<br>
>><br>
>> * If people are informed that a "256-bit private key" is=
what ultimately<br>
>> controls their balances, it could prompt confusion like, "if =
each key<br>
>> has 256-bits, will I need 40 keys to hold 10,000.00 bits?"<br=
>
>><br>
>> * When people learn that there are 8 bits to a byte, they may thin=
k,<br>
>> "OK, my wallet holding my 80,000.00 bits will then take up 10=
kilobytes".<br>
>><br>
>> * When people naturally extend "bit" into "kilobits=
" to mean "1000<br>
>> bits", then the new coinage "kilobits" will mean th=
e exact same amount<br>
>> (100,000 satoshi) as many have already been calling "millibit=
s".<br>
>><br>
>> I believe it'd be best to pick a new made-up single-syllable w=
ord as a<br>
>> synonym for "microbitcoin", and I've laid out the ca=
se for "zib" as that<br>
>> word at <<a href=3D"http://zibcoin.org" target=3D"_blank">http:=
//zibcoin.org</a>>.<br>
>><br>
>> 'Zib' also lends itself to an expressive unicode symbol, &=
#39;=C6=B5'<br>
>> (Z-with-stroke), that remains distinctive even if it loses its str=
oke or<br>
>> gets case-reversed. (Comparatively, all 'b'-derived symbol=
s for<br>
>> data-bits, bitcoins, or '100 satoshi bits' risk collision =
in contexts<br>
>> where subtleties of casing/stroking are lost.)<br>
>><br>
>> (There's summary of more problems with "bit" in the =
<a href=3D"http://zibcoin.org" target=3D"_blank">zibcoin.org</a> FAQ =C2=A0=
at:<br>
>> <<a href=3D"http://zibcoin.org/faq#why-not-bits-to-mean-microbi=
tcoins" target=3D"_blank">http://zibcoin.org/faq#why-not-bits-to-mean-micro=
bitcoins</a>>.)<br>
>><br>
>> - Gordon<br>
>><br>
>> On 5/1/14, 3:35 PM, Aaron Voisine wrote:<br>
>>> I'm also a big fan of standardizing on microBTC as the sta=
ndard unit.<br>
>>> I didn't like the name "bits" at first, but the =
more I think about it,<br>
>>> the more I like it. The main thing going for it is the fact th=
at it's<br>
>>> part of the name bitcoin. If Bitcoin is the protocol and netwo=
rk, bits<br>
>>> are an obvious choice for the currency unit.<br>
>>><br>
>>> I would like to propose using Unicode character U+0180, lowerc=
ase b<br>
>>> with stroke, as the symbol to represent the microBTC denominat=
ion,<br>
>>> whether we call bits or something else:<br>
>>> =C2=A0 <a href=3D"http://www.fileformat.info/info/unicode/char=
/0180/index.htm" target=3D"_blank">http://www.fileformat.info/info/unicode/=
char/0180/index.htm</a><br>
>>><br>
>>> Another candidate is Unicode character U+2422, the blank symbo=
l, but I<br>
>>> prefer stroke b.<br>
>>> <a href=3D"http://www.fileformat.info/info/unicode/char/2422/i=
ndex.htm" target=3D"_blank">http://www.fileformat.info/info/unicode/char/24=
22/index.htm</a><br>
>>><br>
>>> Aaron<br>
>>><br>
>>> There's no trick to being a humorist when you have the who=
le<br>
>>> government working for you -- Will Rodgers<br>
>>><br>
>>>> On Apr 21, 2014 5:41 AM, "Pieter Wuille" <pie=
ter.wuille@gm...> wrote:<br>
>>>><br>
>>>>> On Apr 21, 2014 3:37 AM, "Un Ix" <slashde=
vnull@...> wrote:<br>
>>>>><br>
>>>>> Something tells me this would be reduced to a single s=
yllable in common<br>
>>>>> usage I.e. bit.<br>
>>>><br>
>>>> What units will be called colloquially is not something de=
velopers will<br>
>>>> determine. It will vary, depend on language and culture, a=
nd is not<br>
>>>> relevant to this discussion in my opinion.<br>
>>>><br>
>>>> It may well be that people in some geographic or language =
area will end up<br>
>>>> (or for a while) calling 1e-06 BTC "bits". That&=
#39;s fine, but using that as<br>
>>>> "official" name in software would be very strang=
e and potentially confusing<br>
>>>> in my opinion. As mentioned by others, that would seem to =
me like calling<br>
>>>> dollars "bucks" in bank software. Nobody seems t=
o have a problem with<br>
>>>> having colloquial names, but "US dollar" or &quo=
t;euro" are far less ambiguous<br>
>>>> than "bit". I think we need a more distinctive n=
ame.<br>
>>>><br>
>>>> --<br>
>>>> Pieter<br>
>>><br>
>>> --------------------------------------------------------------=
----------------<br>
>>> "Accelerate Dev Cycles with Automated Cross-Browser Testi=
ng - For FREE<br>
>>> Instantly run your Selenium tests across 300+ browser/OS combo=
s. =C2=A0Get<br>
>>> unparalleled scalability from the best Selenium testing platfo=
rm available.<br>
>>> Simple to use. Nothing to install. Get started now for free.&q=
uot;<br>
>>> <a href=3D"http://p.sf.net/sfu/SauceLabs" target=3D"_blank">ht=
tp://p.sf.net/sfu/SauceLabs</a><br>
>>> _______________________________________________<br>
>>> Bitcoin-development mailing list<br>
>>> <a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">B=
itcoin-development@lists.sourceforge.net</a><br>
>>> <a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoi=
n-development" target=3D"_blank">https://lists.sourceforge.net/lists/listin=
fo/bitcoin-development</a><br>
>>><br>
>><br>
>> ------------------------------------------------------------------=
------------<br>
>> "Accelerate Dev Cycles with Automated Cross-Browser Testing -=
For FREE<br>
>> Instantly run your Selenium tests across 300+ browser/OS combos. =
=C2=A0Get<br>
>> unparalleled scalability from the best Selenium testing platform a=
vailable.<br>
>> Simple to use. Nothing to install. Get started now for free."=
<br>
>> <a href=3D"http://p.sf.net/sfu/SauceLabs" target=3D"_blank">http:/=
/p.sf.net/sfu/SauceLabs</a><br>
>> _______________________________________________<br>
>> Bitcoin-development mailing list<br>
>> <a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitco=
in-development@lists.sourceforge.net</a><br>
>> <a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/b=
itcoin-development</a><br>
><br>
> ----------------------------------------------------------------------=
--------<br>
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For=
FREE<br>
> Instantly run your Selenium tests across 300+ browser/OS combos. =C2=
=A0Get<br>
> unparalleled scalability from the best Selenium testing platform avail=
able.<br>
> Simple to use. Nothing to install. Get started now for free."<br>
> <a href=3D"http://p.sf.net/sfu/SauceLabs" target=3D"_blank">http://p.s=
f.net/sfu/SauceLabs</a><br>
> _______________________________________________<br>
> Bitcoin-development mailing list<br>
> <a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-d=
evelopment@lists.sourceforge.net</a><br>
> <a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-develo=
pment" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitco=
in-development</a><br>
<br>
---------------------------------------------------------------------------=
---<br>
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE=
<br>
Instantly run your Selenium tests across 300+ browser/OS combos. =C2=A0Get<=
br>
unparalleled scalability from the best Selenium testing platform available.=
<br>
Simple to use. Nothing to install. Get started now for free."<br>
<a href=3D"http://p.sf.net/sfu/SauceLabs" target=3D"_blank">http://p.sf.net=
/sfu/SauceLabs</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>
</div></div></blockquote></div><br></div>
--001a11339a762262cd04f8810873--
|