Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wcc7B-0004v9-3f for bitcoin-development@lists.sourceforge.net; Tue, 22 Apr 2014 14:56:05 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.170 as permitted sender) client-ip=209.85.212.170; envelope-from=natanael.l@gmail.com; helo=mail-wi0-f170.google.com; Received: from mail-wi0-f170.google.com ([209.85.212.170]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wcc77-00029t-F2 for bitcoin-development@lists.sourceforge.net; Tue, 22 Apr 2014 14:56:05 +0000 Received: by mail-wi0-f170.google.com with SMTP id bs8so3211505wib.5 for ; Tue, 22 Apr 2014 07:55:55 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.181.11.229 with SMTP id el5mr16454755wid.43.1398178555323; Tue, 22 Apr 2014 07:55:55 -0700 (PDT) Received: by 10.194.54.34 with HTTP; Tue, 22 Apr 2014 07:55:54 -0700 (PDT) Received: by 10.194.54.34 with HTTP; Tue, 22 Apr 2014 07:55:54 -0700 (PDT) In-Reply-To: <89C372C7-522F-472A-9A75-656E481321A0@bitsofproof.com> References: <3A69904F-0A3D-42E9-9DE7-067874E710BB@bitsofproof.com> <5354DC68.5040602@gmx.de> <89C372C7-522F-472A-9A75-656E481321A0@bitsofproof.com> Date: Tue, 22 Apr 2014 16:55:54 +0200 Message-ID: From: Natanael To: Tamas Blummer Content-Type: multipart/alternative; boundary=f46d043c80041f6cc204f7a2d0fd X-Spam-Score: -0.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 (natanael.l[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 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 X-Headers-End: 1Wcc77-00029t-F2 Cc: 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Apr 2014 14:56:05 -0000 --f46d043c80041f6cc204f7a2d0fd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I am in favor of xbit, my only concern is if average Joes will consider that name "stupid" (like various attempts at "cool" branding with unusual letters like Q, X, Z, etc). We should see if we can get support for it in the community and if there would be any notable opposition against it or not. If there's no significant opposition and most people are in favor, I'd say go ahead. - Sent from my phone Den 21 apr 2014 11:38 skrev "Tamas Blummer" : > Thomas V: > > Your proposal misses the points that: > > - this is about a unit with 1e-6 Bitcoins or 100 satoshis. > - it is not about people who know Bitcoin and are techies, but about thos= e > who don=E2=80=99t and aren=E2=80=99t. > > The reasons for such a unit are more than shifting the comma some places > for convinience, > but to align Bitcoin with capabilities of existing financial software and > customs of finance and average people, > and ISO standard of currency abbreviations. > > bit and XBT seems to check the boxes. > > I would love to have some feedback on xbit as per my previous mail. > > Regards, > > Tamas Blummer > http://bitsofproof.com > > > > -------------------------------------------------------------------------= ----- > Start Your Social Network Today - Download eXo Platform > Build your Enterprise Intranet with eXo Platform Software > Java Based Open Source Intranet - Social, Extensible, Cloud Ready > Get Started Now And Turn Your Intranet Into A Collaboration Platform > http://p.sf.net/sfu/ExoPlatform > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > --f46d043c80041f6cc204f7a2d0fd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I am in favor of xbit, my only concern is if average Joes wi= ll consider that name "stupid" (like various attempts at "co= ol" branding with unusual letters like Q, X, Z, etc). We should see if= we can get support for it in the community and if there would be any notab= le opposition against it or not. If there's no significant opposition a= nd most people are in favor, I'd say go ahead.

- Sent from my phone

Den 21 apr 2014 11:38 skrev "Tamas Blummer&= quot; <tamas@bitsofproof.com>:
Thomas V:=C2=A0

Your= proposal misses the points that:

- this is about = a unit with 1e-6 Bitcoins or 100 satoshis.=C2=A0
- it is not abou= t people who know Bitcoin and are techies, but about those who don=E2=80=99= t and aren=E2=80=99t.

The reasons for such a unit are more than shifting the = comma some places for convinience,=C2=A0
but to align Bitcoin wit= h capabilities of existing financial software and customs of finance and av= erage people,
and ISO standard of currency abbreviations.

b= it and XBT seems to check the boxes.=C2=A0

I would= love to have some feedback on xbit as per my previous mail.

Regards,
Tamas Blummer
http://bitsofproof.com


---------------------------------= ---------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.n= et/sfu/ExoPlatform
_______________________________________________ Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--f46d043c80041f6cc204f7a2d0fd--