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 ) id 1Vh7jL-0005g7-DO for bitcoin-development@lists.sourceforge.net; Fri, 15 Nov 2013 00:57:51 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.53 as permitted sender) client-ip=209.85.216.53; envelope-from=etotheipi@gmail.com; helo=mail-qa0-f53.google.com; Received: from mail-qa0-f53.google.com ([209.85.216.53]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Vh7jK-0006wX-Dq for bitcoin-development@lists.sourceforge.net; Fri, 15 Nov 2013 00:57:51 +0000 Received: by mail-qa0-f53.google.com with SMTP id k4so174585qaq.12 for ; Thu, 14 Nov 2013 16:57:45 -0800 (PST) X-Received: by 10.229.101.74 with SMTP id b10mr6822734qco.8.1384477064930; Thu, 14 Nov 2013 16:57:44 -0800 (PST) Received: from [192.168.1.85] (c-76-111-96-126.hsd1.md.comcast.net. [76.111.96.126]) by mx.google.com with ESMTPSA id jw9sm1158842qeb.2.2013.11.14.16.57.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 14 Nov 2013 16:57:44 -0800 (PST) Message-ID: <52857187.4060506@gmail.com> Date: Thu, 14 Nov 2013 19:57:43 -0500 From: Alan Reiner User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <52856CC7.5050103@gmail.com> In-Reply-To: <52856CC7.5050103@gmail.com> 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. 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: doubleclick.net] -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 (etotheipi[at]gmail.com) -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: 1Vh7jK-0006wX-Dq Subject: Re: [Bitcoin-development] moving the default display to mbtc 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: Fri, 15 Nov 2013 00:57:51 -0000 I disagree. There's a real perception and usability issue with the current interface combined with the current price. People are intimidated by the current system, even though the price really reflects Bitcoin starting to spread its wings (maybe prematurely, bubble-style, but the price will have to get to this point eventually if Bitcoin will thrive at the target scale). Bitcoin's learning curve is hard enough already. As silly as it sounds, feeling "insecure" because you only 0.00032 BTC, and then using too many zeroes when paying for your smoothie are problems that can really turn people off. You say "Let the market sort it out". Sometimes the market needs direction and consistency. Without us doing anything, we just end up with fragmentation and confusion. I'd much prefer we reach a consensus on a path forward and push that path hard. Because there's always resistance to change, and confusion along the way. The easier and more consistent we can make it, the smoother it will be. We want to avoid: "Hey, I'll sell it to you for 382 microbes." "What is a microbe? Is that the same as a XBT?" "I don't know, my wallet uses NBC." "Well how much BTC is it? Okay, just send me 0.00038200 BTC" "Four zeros after the decimal?" "Yeah... oh wait you just sent me 10x" ... Again it sounds silly, but this is a real usability issue. On 11/14/2013 07:37 PM, Daniel F wrote: >> This is a decentralized currency, and we should avoid centralizing >> decisions. This is something that impacts the community at large, and >> deserves input and discussion at every level. >> >> I would suggest posting on all possible forums "proposal: switch to >> uBTC, labelled as ISO prefers (XBT?)" and see what sort of discussion >> is generated. If the support is broad, it will be plain from the >> responses if there is a consensus. Perhaps everyone will agree it is >> the best course, and we can make an easy change. >> >> But we need less "core dev fiat" not more :) >> > this seems like such a paint-the-bikeshed problem that it's sure to > generate vast volumes of discussion, waste a lot of people's time, and > all for only a dubious (imo) gain. (case in point - here i am > contributing to it :) ). > > i agree that we should avoid centralizing this. i'll go a step further > and note that the client already has a dropdown allowing individuals to > choose units. merchants are free to choose to price in different units. > exchanges are free to denominate trade in different units. > > i suggest we just let the market do its thing and not get into trying to > 'make a decision' of any sort. > > ------------------------------------------------------------------------------ > DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps > OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access > Free app hosting. Or install the open source package on any LAMP server. > Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! > http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development