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 1Vh6uP-0002sI-O8 for bitcoin-development@lists.sourceforge.net; Fri, 15 Nov 2013 00:05:13 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com designates 74.125.82.44 as permitted sender) client-ip=74.125.82.44; envelope-from=jgarzik@bitpay.com; helo=mail-wg0-f44.google.com; Received: from mail-wg0-f44.google.com ([74.125.82.44]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Vh6uO-0004ts-PP for bitcoin-development@lists.sourceforge.net; Fri, 15 Nov 2013 00:05:13 +0000 Received: by mail-wg0-f44.google.com with SMTP id k14so2867427wgh.35 for ; Thu, 14 Nov 2013 16:05:06 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=hv2fhXxIsmUtuMudShjaUcgqbTuMBks0pm/v0sfyB7s=; b=CjP+D36iKQKO+63bPPIHPH/hkl3zSvuzeJxM7njXOD1Bx30+WcDOjrDcbcxhgweiQj ek5KFoaZh/CUUq42X/T3llsC/l3RsLr6BD/ZWkxli5Gxo24m1cZm6gKfNpOda5xHj8JM HOZVpBwexHlXXZz9UusursXhiSLS91l/LRtqKUY5L16ymcGNY4ZtoXKcnNhU+U6WUeag HGXlPpT/ar8QdMWfczX3fgcpp78NfJlpDW8WwZErzKXb4ABZIl2VIj6z49j918JiOqEn gWZf4KCiAn3UTRFlszNLs+L+wJtdo7rkp7FS5kAHQEwuEbqyTzoA9ymFFS+LnQSO8DGw PTBg== X-Gm-Message-State: ALoCoQlRyC0JuP6R03fifHg8cWDHx26I8eayv3pnJ3bd1E8i37yK1Gx5pyuj019V44YCwdMtP9dP MIME-Version: 1.0 X-Received: by 10.180.198.5 with SMTP id iy5mr5197247wic.45.1384473906643; Thu, 14 Nov 2013 16:05:06 -0800 (PST) Received: by 10.194.164.164 with HTTP; Thu, 14 Nov 2013 16:05:06 -0800 (PST) In-Reply-To: References: Date: Thu, 14 Nov 2013 19:05:06 -0500 Message-ID: From: Jeff Garzik To: Drak Content-Type: text/plain; charset=ISO-8859-1 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 SPF_PASS SPF: sender matches SPF record 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: zikula.org] -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: 1Vh6uO-0004ts-PP Cc: Bitcoin Dev 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:05:13 -0000 On Thu, Nov 14, 2013 at 5:27 PM, Drak wrote: > Unless something is recommended/done by the bitcoin core developers I doubt > much will change at bitcoin user/consumer level. While the sentiment is appreciated, it seems important to gently push back a bit, and remind: 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 :) -- Jeff Garzik Senior Software Engineer and open source evangelist BitPay, Inc. https://bitpay.com/