public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Caldwell <mcaldwell@swipeclock•com>
To: Christophe Biocca <christophe.biocca@gmail•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] "bits": Unit of account
Date: Sun, 20 Apr 2014 16:28:34 -0400	[thread overview]
Message-ID: <4098C706-D67F-474E-9C13-E4C8F56B41ED@swipeclock.com> (raw)
In-Reply-To: <CANOOu=9=TAnaCuyh_P2GqHaguyY39xjhj84HSA_x+6F4MOqM_A@mail.gmail.com>

By culturally neutral I mean we avoid deliberately invoking a cultural reference in the name.  For example "satoshi" would be a reference to Japanese culture just for being a common Japanese name regardless of who Satoshi turns out to be. 

Mike

Sent from my iPhone

> On Apr 20, 2014, at 1:20 PM, "Christophe Biocca" <christophe.biocca@gmail•com> wrote:
> 
> Culturally neutral? "bit" in French phonetically collides with slang
> for phallus ("bitte", with a silent "e"). Apparently it means "louse"
> in Turkish as well.
> 
> Not that this really would be avoidable with any short word (all the
> short possible words are usually taken), but it's not neutral.
> 
>> On Sun, Apr 20, 2014 at 2:43 PM, Oliver Egginger <bitcoin@olivere•de> wrote:
>> Hello,
>> 
>> just my two 'cents':
>> 
>> Terms arises by itself. Just as most people speak of coins when they
>> mean bitcoins. I do not see that bitcoin is currently in common use
>> except for speculation. Therefore no term for smaller units has
>> established yet. No problem in my eyes. Time will tell.
>> 
>> - oliver
>> 
>> 
>> ------------------------------------------------------------------------------
>> Learn Graph Databases - Download FREE O'Reilly Book
>> "Graph Databases" is the definitive new guide to graph databases and their
>> applications. Written by three acclaimed leaders in the field,
>> this first edition is now available. Download your free book today!
>> http://p.sf.net/sfu/NeoTech
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists•sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> 
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/NeoTech
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development



  parent reply	other threads:[~2014-04-20 20:28 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-20 12:35 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 [this message]
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=4098C706-D67F-474E-9C13-E4C8F56B41ED@swipeclock.com \
    --to=mcaldwell@swipeclock$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=christophe.biocca@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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