path: root/d0/04af86b335f31d69bd2cf10195674633375b72

Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mcaldwell@swipeclock.com>) id 1Wgxcv-0001pd-34
	for bitcoin-development@lists.sourceforge.net;
	Sun, 04 May 2014 14:42:49 +0000
Received-SPF: fail (sog-mx-2.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-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.76) id 1Wgxct-0007aM-So
	for bitcoin-development@lists.sourceforge.net;
	Sun, 04 May 2014 14:42:49 +0000
Received: from mxout.myoutlookonline.com (localhost [127.0.0.1])
	by mxout.myoutlookonline.com (Postfix) with ESMTP id BBF548BEF5A;
	Sun,  4 May 2014 10:42:38 -0400 (EDT)
X-Virus-Scanned: by SpamTitan at mail.lan
Received: from HUB023.mail.lan (unknown [10.110.2.1])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by mxout.myoutlookonline.com (Postfix) with ESMTPS id 01D958BEEEE;
	Sun,  4 May 2014 10:42:38 -0400 (EDT)
Received: from MAILR023.mail.lan ([10.110.18.122]) by HUB023.mail.lan
	([10.110.17.23]) with mapi; Sun, 4 May 2014 10:42:53 -0400
From: Mike Caldwell <mcaldwell@swipeclock.com>
To: Aaron Voisine <voisine@gmail.com>
Date: Sun, 4 May 2014 10:42:40 -0400
Thread-Topic: [Bitcoin-development] "bits": Unit of account
Thread-Index: Ac9npxnqPJmGZ1EdTeGiNUUYpo4/Vg==
Message-ID: <AFE68F19-20A8-4FFD-8065-92BDCAF1D3FF@swipeclock.com>
References: <CACq0ZD6EJnG4iwehfcFU-4AhBiNdtyf7eE9iGW8d6rv6327Eug@mail.gmail.com>
	<53644F13.1080203@gmail.com>
	<CACq0ZD7s8tp8GvJhEhZx4T7xMpeZ+tz5HNKQK-p=f=R10NaCmA@mail.gmail.com>
	<CANOOu=9orMZH6fpTfkO8zgwPDmwpA8WW78EKwSTiw2GXn7UCxA@mail.gmail.com>
	<A4150064-81C5-4B39-B696-B4F778531F3B@swipeclock.com>
	<53659234.3020207@gmail.com>
	<CANAnSg1=ap03K-Rxhje0RP-nxt8eWzWiURzXrMBe3Au-bBUBpQ@mail.gmail.com>
	<CACq0ZD7SP==2cMCHnYPiHwh-MWwuWCKVX5T8+3P7xMAG+5i91g@mail.gmail.com>
In-Reply-To: <CACq0ZD7SP==2cMCHnYPiHwh-MWwuWCKVX5T8+3P7xMAG+5i91g@mail.gmail.com>
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: 1Wgxct-0007aM-So
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: Sun, 04 May 2014 14:42:49 -0000

I will drink to that!

Bitte ein Bit! (A Bit please - aka Bitburger Beer)

Mike

Sent from my iPhone

> On May 4, 2014, at 12:17 AM, "Aaron Voisine" <voisine@gmail.com> wrote:
>=20
> Bit by bit, it's become clear that it's a bit much to worry even a
> little bit that overloading the word "bit" would be every bit as bad
> as a two bit horse with the bit between it's teeth that bit the hand
> that feeds it, or a drill bit broken to bits after just a bit of use.
>=20
> Aaron
>=20
> There's no trick to being a humorist when you have the whole
> government working for you -- Will Rodgers
>=20
>=20
>> On Sat, May 3, 2014 at 10:18 PM, Drak <drak@zikula.org> wrote:
>> +1
>>=20
>>> On 4 May 2014 02:06, "Chris Pacia" <ctpacia@gmail.com> wrote:
>>>=20
>>> Absent a concerted effort to move to something else other than 'bits', =
I
>>> would be willing to bet the nomenclature moves in that direction anyway=
.
>>> 'Bits' is just a shorten word for 'millibits' (or microbits, if you
>>> will). It's easier to say and my guess is people would tend to use it
>>> naturally own their own. Kind of like 'bucks' for dollars.
>>>=20
>>> The other synergies are:
>>> -bit is part of the word Bitcoin. The currency unit bit is part of a
>>> whole bitcoin.
>>> -bit symbolically represents the tech nature of the bitcoin.
>>> -bit used to be a unit of money way back when. This largely reclaims it=
.
>>> -when used as money bit when in references to a precession metal coin.
>>> The name 'bitcoin' references that as well as the mimicking of the gold
>>> standard in the protocol rules.
>>>=20
>>> All around I don't think there is a better fit. I doubt people will get
>>> confused by it. The context it's used in will distinguish it from other
>>> uses of the word.
>>>=20
>>>> On 05/03/2014 12:27 PM, Mike Caldwell wrote:
>>>> I agree with the sentiment that most people don't understand either
>>>> computer science or Bitcoin.  The goal of getting people to understand
>>>> enough about Bitcoin to use it is achievable and a goal that is "in sc=
ope"
>>>> of our efforts. Getting them to understand computer science at large a=
t the
>>>> same time, less so.
>>>>=20
>>>> The fact that people routinely confuse RAM and hard drive sizes has mu=
ch
>>>> to do with the fact that the average lay person has little need to
>>>> prioritize this as something to keep in the forefront.  They don't get
>>>> "horribly" confused, they just simply don't get worked up over what lo=
oks to
>>>> them like a rounding error, much to the dismay of anyone who believes =
that
>>>> everyone should be an expert at computer science.  The average joe may
>>>> assess (accurately from his perspective) that the distinction isn't
>>>> important enough to merit significant mental resources and he is justi=
fied
>>>> in not expending them that way even if someone else thinks he should.
>>>>=20
>>>> Poor understanding is precisely what a proper effort to name this woul=
d
>>>> be to avoid.  It is not frill or aesthetics, it is a planned targeting=
 of
>>>> language to achieve the clearest communication to the widest possible =
target
>>>> audience using the language most likely to be understood by them in li=
ght of
>>>> our objectives.  It's marketing.
>>>>=20
>>>> Mike
>>>>=20
>>>> Sent from my iPhone
>>>>=20
>>>>> On May 3, 2014, at 9:49 AM, "Christophe Biocca"
>>>>> <christophe.biocca@gmail.com> wrote:
>>>>>=20
>>>>> 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 horribl=
y
>>>>> confused between RAM and Hard Drive sizes, because they share the sam=
e
>>>>> units (not that that can be helped, as the units are supposed to be
>>>>> the same, base 1000 vs 1024 notwithstanding).
>>>>>=20
>>>>> 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 issu=
e
>>>>> are making an assumption based on their own lack of confusion. We
>>>>> understand computer science AND Bitcoin. Most people have zero
>>>>> understanding of either.
>>>>>=20
>>>>> Bitcoin already has a ton of issues with terrible names for things:
>>>>>=20
>>>>> - Mining (for transaction validation).
>>>>> - Addresses (which are meant to be one-time use, and don't even reall=
y
>>>>> exist at the network level).
>>>>> - Wallets (which don't hold your bitcoins, can be copied, and all
>>>>> backups can be stolen from equally).
>>>>>=20
>>>>> 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 i=
s
>>>>> 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'v=
e
>>>>> 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).
>>>>>=20
>>>>> It seems downright masochistic to add
>>>>> yet-another-word-that-doesn't-mean-what-you-think-it-means to the pil=
e
>>>>> for no reason other than aesthetics. Are we actively trying to confus=
e
>>>>> people?
>>>>=20
>>>> ----------------------------------------------------------------------=
--------
>>>> "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
>>>=20
>>>=20
>>>=20
>>> -----------------------------------------------------------------------=
-------
>>> "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
>>=20
>>=20
>> ------------------------------------------------------------------------=
------
>> "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 availab=
le.
>> 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
>=20
> -------------------------------------------------------------------------=
-----
> "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