Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WO8vO-0002Pd-4d for bitcoin-development@lists.sourceforge.net; Thu, 13 Mar 2014 16:56:06 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.51 as permitted sender) client-ip=74.125.82.51; envelope-from=allen.piscitello@gmail.com; helo=mail-wg0-f51.google.com; Received: from mail-wg0-f51.google.com ([74.125.82.51]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WO8vM-0007SE-Jd for bitcoin-development@lists.sourceforge.net; Thu, 13 Mar 2014 16:56:06 +0000 Received: by mail-wg0-f51.google.com with SMTP id k14so1127929wgh.22 for ; Thu, 13 Mar 2014 09:55:58 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.180.97.72 with SMTP id dy8mr2427424wib.5.1394729758400; Thu, 13 Mar 2014 09:55:58 -0700 (PDT) Received: by 10.194.76.135 with HTTP; Thu, 13 Mar 2014 09:55:58 -0700 (PDT) In-Reply-To: References: <52852C2D.9020103@gmail.com> <52853D8A.6010501@monetize.io> Date: Thu, 13 Mar 2014 11:55:58 -0500 Message-ID: From: Allen Piscitello To: Bitcoin Development Content-Type: multipart/alternative; boundary=f46d04430670cea78b04f47fd3d9 X-Spam-Score: 1.9 (+) 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 (allen.piscitello[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 2.5 US_DOLLARS_3 BODY: Mentions millions of $ ($NN, NNN, NNN.NN) 1.0 HTML_MESSAGE BODY: HTML included in message -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 0.0 LOTS_OF_MONEY Huge... sums of money X-Headers-End: 1WO8vM-0007SE-Jd 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: Thu, 13 Mar 2014 16:56:06 -0000 --f46d04430670cea78b04f47fd3d9 Content-Type: text/plain; charset=ISO-8859-1 Mike is making an assumption that is not necessary, which is the price of the most commonly used unit should be between is $.50 and $1000. The issue to revisit or not shouldn't require $1,000,000 Bitcoin price. Typing a ton of decimals is incredibly annoying. Doing the mental math in my head is annoying. Even if a cup of coffee costs 3.12345 mBTC, that's a lot more annoying than 3123.45 uBTC. The points that people liked mBTC better than BTC doesn't mean anything when comparing uBTC to mBTC. Many people just stopped thinking at the mBTC level, do not understand the implications involved in switching to uBTC, or even considered uBTC. The idea that we can just poll what people want to give them the ideal experience is also flawed, in that users often don't know what they want until they have it in front of them. There is basically no downside to uBTC, except a few places already switched to mBTC. For exchanges, which are dealing with decimals since they will do BTC/USD rather than the opposite, it might make sense for them to continue to use mBTC or BTC. For wallets and prices for users, especially when there are large decimals since the price is still based on more stable currencies, then converted to Bitcoin, let's switch to what is easiest. I haven't seen a single good argument for keeping it in mBTC (other than some people already did it). On the other hand, I've seen numerous great reasons for switching to uBTC. My two cents. On Thu, Mar 13, 2014 at 11:39 AM, Melvin Carvalho wrote: > > > > On 13 March 2014 16:50, Mike Hearn wrote: > >> On Thu, Mar 13, 2014 at 3:32 PM, Jeff Garzik wrote: >> >>> Such hand-wavy, data-free logic is precisely why community >>> coordination is preferred to random apps making random decisions in >>> this manner. >>> >> >> That ship sailed months ago. If you wanted a big push for uBTC, then >> would have been the time. Though given that it'd have made lots of normal >> balances incredibly huge, perhaps it's a good thing that didn't happen. >> Also "milli" is a unit people encounter in daily life whereas micro isn't. >> Is it milli / micro / nano or milli / nano / micro? I bet a lot of people >> would get that wrong. >> >> If you have to export to financial packages that can't handle fractional >> pennies, then by all means represent prices in whatever units you like for >> that purpose, but in software designed for ordinary people in everyday life >> mBTC is a pretty good fit. >> >> Besides, fractional pennies crop up in existing currencies too (the >> famous Verizon Math episode showed this), so if a financial package insists >> on rounding to 2dp then I guess it may sometimes do the wrong thing in some >> business cases already. >> >> Fundamentally, more than two decimal places tends to violate the >>> Principle Of Least Astonishment with many humans, and as a result, >>> popular software systems have been written with that assumption. >> >> >> Lots of people use currencies that don't have any fractional components >> at all ! So perhaps all prices should be denominated in satoshis to ensure >> that they're not surprised :) >> >> The (number) line has to be drawn somewhere. Wallets are free to suppress >> more than 2dp of precision and actually Andreas' app lets you choose your >> preferred precision. So I think in the end it won't matter a whole lot, if >> the defaults end up being wrong people can change them until wallet authors >> catch up. >> > > +1 agree with Mike on everything > > A couple of points: > > 1. bitcoinity already switched to mbtc aka millitbits ( > https://en.bitcoin.it/wiki/MilliBit ) and it was positively recieved, > they got quite a few donations > > 2. If you watch Gavin's talk at the CFR he suggests the community comes to > a consensus through implementations rather than top down decision making > (If I understood correctly) > > I think it's up to wallet maintainers whether to switch the default. > > > >> >> >> ------------------------------------------------------------------------------ >> 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/13534_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/13534_NeoTech > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > --f46d04430670cea78b04f47fd3d9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Mike is making an assumption that is not necessary, which = is the price of the most commonly used unit should be between is $.50 and $= 1000. =A0The issue to revisit or not shouldn't require $1,000,000 Bitco= in price. =A0Typing a ton of decimals is incredibly annoying. =A0Doing the = mental math in my head is annoying. =A0Even if a cup of coffee costs 3.1234= 5 mBTC, that's a lot more annoying than 3123.45 uBTC.

The points that people liked mBTC better than BTC doesn'= t mean anything when comparing uBTC to mBTC. =A0Many people just stopped th= inking at the mBTC level, do not understand the implications involved in sw= itching to uBTC, or even considered uBTC. =A0The idea that we can just poll= what people want to give them the ideal experience is also flawed, in that= users often don't know what they want until they have it in front of t= hem.

There is basically no downside to uBTC, except a few pl= aces already switched to mBTC. =A0For exchanges, which are dealing with dec= imals since they will do BTC/USD rather than the opposite, it might make se= nse for them to continue to use mBTC or BTC. =A0For wallets and prices for = users, especially when there are large decimals since the price is still ba= sed on more stable currencies, then converted to Bitcoin, let's switch = to what is easiest.

I haven't seen a single good argument for keeping i= t in mBTC (other than some people already did it). =A0On the other hand, I&= #39;ve seen numerous great reasons for switching to uBTC.

My two cents.


On Thu, Mar 13, 2014 at 11:39 AM, Melvin Carvalho <melvincarvalho@gmail.com> wrote:



On 13 March 2= 014 16:50, Mike Hearn <mike@plan99.net> wrote:
On Thu, Mar 13, 2014 at = 3:32 PM, Jeff Garzik <jgarzik@bitpay.com> wrote:
Such hand-wavy, data= -free logic is precisely why community
coordination is preferred to random apps making random decisions in
this manner.

That ship sailed mon= ths ago. If you wanted a big push for uBTC, then would have been the time. = Though given that it'd have made lots of normal balances incredibly hug= e, perhaps it's a good thing that didn't happen. Also "milli&q= uot; is a unit people encounter in daily life whereas micro isn't. Is i= t milli / micro / nano or milli / nano / micro? I bet a lot of people would= get that wrong.

If you have to export to financial packages that can= 9;t handle fractional pennies, then by all means represent prices in whatev= er units you like for that purpose, but in software designed for ordinary p= eople in everyday life mBTC is a pretty good fit.
=A0
Besides, fractional pennies crop up in existing currenci= es too (the famous Verizon Math episode showed this), so if a financial pac= kage insists on rounding to 2dp then I guess it may sometimes do the wrong = thing in some business cases already.

Fundamenta= lly, more than two decimal places tends to violate the
Principle Of Least Astonishment with many humans, and as a result,
popular software systems have been written with that assumption.

Lots of people use currencies that don't ha= ve any fractional components at all ! So perhaps all prices should be denom= inated in satoshis to ensure that they're not surprised :)

The (number) line has to be drawn somewhere. Wallets ar= e free to suppress more than 2dp of precision and actually Andreas' app= lets you choose your preferred precision. So I think in the end it won'= ;t matter a whole lot, if the defaults end up being wrong people can change= them until wallet authors catch up.

+1 agree wit= h Mike on everything

A couple of points:

1. bitcoinity already switched to mbtc aka millitbits ( https://en.bitcoin.it/wiki= /MilliBit ) and it was positively recieved, they got quite a few donati= ons

2. If you watch Gavin's talk at the CFR he su= ggests the community comes to a consensus through implementations rather th= an top down decision making (If I understood correctly)

I think it's up to wallet maintainers whether to switch the default.=A0=

=A0

-----------------------------------------------------------------------= -------
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/13534_NeoTech
_____________________________________________= __
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment



-----------------------------------------------------------------------= -------
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/13534_NeoTech
_____________________________________________= __
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment


--f46d04430670cea78b04f47fd3d9--