From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wgks3-00027A-5f for bitcoin-development@lists.sourceforge.net; Sun, 04 May 2014 01:05:35 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.192.41 as permitted sender) client-ip=209.85.192.41; envelope-from=ctpacia@gmail.com; helo=mail-qg0-f41.google.com; Received: from mail-qg0-f41.google.com ([209.85.192.41]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wgks1-0004fs-Sk for bitcoin-development@lists.sourceforge.net; Sun, 04 May 2014 01:05:35 +0000 Received: by mail-qg0-f41.google.com with SMTP id j107so6358337qga.28 for ; Sat, 03 May 2014 18:05:28 -0700 (PDT) X-Received: by 10.224.49.67 with SMTP id u3mr34098410qaf.63.1399165528361; Sat, 03 May 2014 18:05:28 -0700 (PDT) Received: from [192.168.1.3] (pool-72-73-205-174.cmdnnj.east.verizon.net. [72.73.205.174]) by mx.google.com with ESMTPSA id r4sm7571710qat.16.2014.05.03.18.05.27 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 03 May 2014 18:05:28 -0700 (PDT) Message-ID: <53659234.3020207@gmail.com> Date: Sat, 03 May 2014 21:04:52 -0400 From: Chris Pacia User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Christophe Biocca References: <53644F13.1080203@gmail.com> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (ctpacia[at]gmail.com) -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [209.85.192.41 listed in list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Wgks1-0004fs-Sk Cc: Bitcoin Development 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 May 2014 01:05:35 -0000 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. 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. 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. 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 scope" of our efforts. Getting them to understand computer science at large at the same time, less so. > > The fact that people routinely confuse RAM and hard drive sizes has much 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 looks 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 justified in not expending them that way even if someone else thinks he should. > > Poor understanding is precisely what a proper effort to name this would 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 light of our objectives. It's marketing. > > Mike > > Sent from my iPhone > >> On May 3, 2014, at 9:49 AM, "Christophe Biocca" 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? > ------------------------------------------------------------------------------ > "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 >