From: Chris Pacia <ctpacia@gmail.com>
To: Wladimir <laanwj@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] "bits": Unit of account
Date: Sun, 20 Apr 2014 12:30:12 -0400 [thread overview]
Message-ID: <CAB+qUq4m0-T6iL3rampmemVam5mgFScTOBCM3XrgXvUUJ12X_A@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJBWwstMjKR-A6RyyaA3S4E1d_qapMzyrFkgHNxp__XqDg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 858 bytes --]
You're correct, my impression of the term is based of what I experience in
the US. If it is more widely used in other cultures that should be a
consideration.
On Apr 20, 2014 12:27 PM, "Wladimir" <laanwj@gmail.com> wrote:
> On Sun, Apr 20, 2014 at 6:19 PM, Chris Pacia <ctpacia@gmail.com> wrote:
> > The term bit is really only overloaded for those who are techy. 95% of
> the
> > population never uses the term bit in their daily lives and I doubt most
> > could even name one use of the term.
> > Plus bit used to be a unit of money way back when, so this is kind of
> > reclaiming it. I think it's a great fit.
>
> That's a very anglocentric way of thinking.
>
> Here in the Netherlands, a "bit" is something you put in a horses's
> mouth. It's also used as imported word (in the information sense).
> We've never used the term for money.
>
> Wladimir
>
[-- Attachment #2: Type: text/html, Size: 1236 bytes --]
next prev parent reply other threads:[~2014-04-20 16:30 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 [this message]
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
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=CAB+qUq4m0-T6iL3rampmemVam5mgFScTOBCM3XrgXvUUJ12X_A@mail.gmail.com \
--to=ctpacia@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=laanwj@gmail.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