Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of me.com
	designates 17.172.220.237 as permitted sender)
	client-ip=17.172.220.237; envelope-from=jeanpaulkogelman@me.com;
	helo=st11p02mm-asmtp002.mac.com; 
MIME-version: 1.0
Content-type: multipart/alternative;
	boundary="Boundary_(ID_PDmc9IuD8uhb1Y4RrYR6tA)"
To: Luke-Jr <luke@dashjr.org>
From: Jean-Paul Kogelman <jeanpaulkogelman@me.com>
Date: Sat, 16 Nov 2013 01:19:06 +0000 (GMT)
Message-id: <365382c5-d86c-4e54-8b47-810bf4a758c2@me.com>
In-reply-to: <201311160110.42132.luke@dashjr.org>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] moving the default display to mbtc
Precedence: list


--Boundary_(ID_PDmc9IuD8uhb1Y4RrYR6tA)
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: quoted-printable

=0A=0AOn Nov 15, 2013, at 05:10 PM, Luke-Jr <luke@dashjr.org> wrote:=0A=0A=
On Saturday, November 16, 2013 12:41:56 AM Drak wrote:=0ASo "a payment cle=
ars after one confirmation, but you might want to wait=0Auntil the payment=
 has been confirmed n times".=0AThen at least you are not using the same w=
ord for two different meanings=0Aand you're using stuff more familiar in p=
opular lexicon.=0AI dont think it's helpful for users if we use the word "=
blocks".=0A=0A"Confirmations" in a numeric context isn't correct, though. =
We're using to it =0Abecause we've been using Bitcoin so long, but to the =
average person they would =0Aexpect it to mean something more than it is. =
If not referring to blocks, then =0Aperhaps "witnessed N times"?=0A=0AWhy =
not call it "Clearing" for transactions with < 6 confirmations and "Cleare=
d" for >=3D 6?=0A=A0=0AThe round ticker should be enough of an indication =
of the progress.=0A=0A=0A=

--Boundary_(ID_PDmc9IuD8uhb1Y4RrYR6tA)
Content-type: multipart/related;
	boundary="Boundary_(ID_JkWD4sVo9JeP/LVwHEhalQ)"; type="text/html"


--Boundary_(ID_JkWD4sVo9JeP/LVwHEhalQ)
Content-type: text/html; CHARSET=US-ASCII
Content-transfer-encoding: quoted-printable

<html><body><div><br><br>On Nov 15, 2013, at 05:10 PM, Luke-Jr &lt;luke@dashjr.org&gt;=
 wrote:<br><br></div><div><blockquote type=3D"cite"><div class=3D"msg-quot=
e"><div class=3D"_stretch">On Saturday, November 16, 2013 12:41:56 AM Drak=
 wrote:<br><blockquote class=3D"quoted-plain-text" type=3D"cite">So "a pay=
ment clears after one confirmation, but you might want to wait</blockquote=
><blockquote class=3D"quoted-plain-text" type=3D"cite">until the payment h=
as been confirmed n times".</blockquote><blockquote class=3D"quoted-plain-=
text" type=3D"cite">Then at least you are not using the same word for two =
different meanings</blockquote><blockquote class=3D"quoted-plain-text" typ=
e=3D"cite">and you're using stuff more familiar in popular lexicon.</block=
quote><blockquote class=3D"quoted-plain-text" type=3D"cite">I dont think i=
t's helpful for users if we use the word "blocks".</blockquote><br> "Confi=
rmations" in a numeric context isn't correct, though. We're using to it <b=
r> because we've been using Bitcoin so long, but to the average person the=
y would <br> expect it to mean something more than it is. If not referring=
 to blocks, then <br> perhaps "witnessed N times"?<br> </div></div></block=
quote><span><div><span><br></span></div><div><span>Why not call it "Cleari=
ng" for transactions with &lt; 6 confirmations and "Cleared" for &gt;=3D 6=
?</span></div>&nbsp;</span></div><div>The round ticker should be enough of=
 an indication of the progress.</div><div><br></div><div><br></div></body></html>=

--Boundary_(ID_JkWD4sVo9JeP/LVwHEhalQ)--

--Boundary_(ID_PDmc9IuD8uhb1Y4RrYR6tA)--