public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Un Ix <slashdevnull@hotmail.com>
To: Tamas Blummer <tamas@bitsofproof.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] "bits": Unit of account
Date: Mon, 21 Apr 2014 20:14:25 +0800	[thread overview]
Message-ID: <BLU402-EAS244A4EDF53E0612810DFF06C65E0@phx.gbl> (raw)
In-Reply-To: <B54236EC-1B6A-4DA8-85E8-F3C0B11CDE8C@bitsofproof.com>

[-- Attachment #1: Type: text/plain, Size: 2626 bytes --]

Tamas,

"xbit" is only a typo or spelling error away from "XBT", and some folks may assume they refer to the same unit of measure, not knowing the new currency system as developers here do.

From your email, I got the idea of using "x" as a suffix at the end of a number of bits e.g. 17500x, like cents or centavos. I guess this might clash with formal S.I. notation but it's easy to read and has less ambiguity, IMHO.

> On 21/04/2014, at 2:21 pm, "Tamas Blummer" <tamas@bitsofproof.com> wrote:
> 
> Here is one to please those looking for a “fully qualified” slang word, that links with the official XBT:
> 
> xbit (spoken: ex-bit) would rationalise XBT (where X comes from supranational use) and is unique.
> 
> I personally associate from x to six also supporting the 1e-6 divisor of Bitcoin.
> 
> Regarding XBT: No matter who used it for what. The way Bloomberg will use it will define its use in finance,
> and since that did not happen yet, we are not late to shape.
> 
> Regards,
> 
> Tamas Blummer
> http://bitsofproof.com
> 
>> On 21.04.2014, at 07:41, Pieter Wuille <pieter.wuille@gmail.com> wrote:
>> 
>> 
>> On Apr 21, 2014 3:37 AM, "Un Ix" <slashdevnull@hotmail.com> 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 with having colloquial names, but "US dollar" or "euro" are far less ambiguous than "bit". I think we need a more distinctive name.
>> 
>> -- 
>> Pieter
>> ------------------------------------------------------------------------------
>> Start Your Social Network Today - Download eXo Platform
>> Build your Enterprise Intranet with eXo Platform Software
>> Java Based Open Source Intranet - Social, Extensible, Cloud Ready
>> Get Started Now And Turn Your Intranet Into A Collaboration Platform
>> http://p.sf.net/sfu/ExoPlatform_______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> 

[-- Attachment #2: Type: text/html, Size: 6605 bytes --]

  reply	other threads:[~2014-04-21 12:14 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-20 12:35 [Bitcoin-development] "bits": Unit of account Mike Gehl
2014-04-20 13:15 ` Rob Golding
2014-04-20 14:28   ` Tamas Blummer
2014-04-20 14:52     ` Christophe Biocca
2014-04-21  8:52       ` Thomas Voegtlin
2014-04-21  9:34         ` Tamas Blummer
2014-04-22 14:55           ` Natanael
2014-04-20 14:53     ` Pieter Wuille
2014-04-20 15:05       ` Tamas Blummer
2014-04-20 15:50         ` Alan Reiner
2014-04-20 16:19           ` Chris Pacia
2014-04-20 16:27             ` Wladimir
2014-04-20 16:30               ` Chris Pacia
2014-04-22 13:51               ` Aaron Axvig
2014-04-23  9:44                 ` Danny Hamilton
2014-04-23  9:56                   ` Tamas Blummer
2014-04-23 11:48                     ` Chris D'Costa
2014-04-20 16:23           ` Erik Garrison
2014-04-20 16:30             ` Alan Reiner
2014-04-20 16:56               ` Mike Caldwell
2014-04-20 17:47                 ` Jannis Froese
2014-04-20 18:10                 ` Pavol Rusnak
2014-04-20 17:42 ` Arne Brutschy
2014-04-20 18:11   ` Mike Caldwell
2014-04-20 18:22     ` Arne Brutschy
2014-04-20 18:34       ` Mike Caldwell
2014-04-20 18:43     ` Oliver Egginger
2014-04-20 19:19       ` Christophe Biocca
2014-04-20 19:32         ` Gmail
2014-04-20 20:28         ` Mike Caldwell
2014-04-21  0:16           ` Justin A
2014-04-21  1:18             ` Mike Caldwell
2014-04-21  1:33               ` Un Ix
2014-04-21  3:34                 ` Mike Caldwell
2014-04-21  4:08                   ` Christopher Paika
2014-04-21  5:41                 ` Pieter Wuille
2014-04-21  5:51                   ` Tamas Blummer
2014-04-21  6:21                   ` Tamas Blummer
2014-04-21 12:14                     ` Un Ix [this message]
2014-04-21 12:24                       ` Tamas Blummer
2014-05-01 22:35 Aaron Voisine
2014-05-03  2:06 ` Gordon Mohr
2014-05-03  5:41   ` Aaron Voisine
2014-05-03 15:48     ` Christophe Biocca
2014-05-03 16:02       ` slush
2014-05-03 16:10         ` Tamas Blummer
2014-05-03 16:27       ` Mike Caldwell
2014-05-04  1:04         ` Chris Pacia
2014-05-04  5:18           ` Drak
2014-05-04  6:15             ` Aaron Voisine
2014-05-04  6:23               ` Un Ix
2014-05-04  6:27               ` Wladimir
2014-05-04  6:36                 ` Tamas Blummer
2014-05-04  6:59                   ` Wladimir
2014-05-04 14:42               ` Mike Caldwell
2014-05-05 22:33     ` Gordon Mohr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BLU402-EAS244A4EDF53E0612810DFF06C65E0@phx.gbl \
    --to=slashdevnull@hotmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=tamas@bitsofproof.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox