From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VhUXZ-0005gi-0y for bitcoin-development@lists.sourceforge.net; Sat, 16 Nov 2013 01:19:13 +0000 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; Received: from st11p02mm-asmtp002.mac.com ([17.172.220.237]) by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1VhUXY-0000HT-4t for bitcoin-development@lists.sourceforge.net; Sat, 16 Nov 2013 01:19:12 +0000 Received: from st11p02mm-spool001.mac.com ([17.172.220.246]) by st11p02mm-asmtp002.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTP id <0MWC002DU0ZUMR00@st11p02mm-asmtp002.mac.com> for bitcoin-development@lists.sourceforge.net; Sat, 16 Nov 2013 01:19:06 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794,1.0.14,0.0.0000 definitions=2013-11-15_07:2013-11-15, 2013-11-15, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1308280000 definitions=main-1311150215 MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_PDmc9IuD8uhb1Y4RrYR6tA)" Received: from localhost ([17.172.220.223]) by st11p02mm-spool001.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTP id <0MWC006DP0ZU8J90@st11p02mm-spool001.mac.com>; Sat, 16 Nov 2013 01:19:06 +0000 (GMT) To: Luke-Jr From: Jean-Paul Kogelman Date: Sat, 16 Nov 2013 01:19:06 +0000 (GMT) X-Mailer: iCloud MailClient1U43 MailServer1U25.15099 X-Originating-IP: [159.153.138.53] Message-id: <365382c5-d86c-4e54-8b47-810bf4a758c2@me.com> In-reply-to: <201311160110.42132.luke@dashjr.org> X-Spam-Score: -0.5 (/) 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: dashjr.org] 1.0 HTML_MESSAGE BODY: HTML included in message 0.0 MIME_QP_LONG_LINE RAW: Quoted-printable line longer than 76 chars X-Headers-End: 1VhUXY-0000HT-4t 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: Sat, 16 Nov 2013 01:19:13 -0000 --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 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


On Nov 15, 2013, at 05:10 PM, Luke-Jr <luke@dashjr.org>= wrote:

On Saturday, November 16, 2013 12:41:56 AM Drak= wrote:
So "a pay= ment clears after one confirmation, but you might want to wait
until the payment h= as been confirmed n times".
Then at least you are not using the same word for two = different meanings
and you're using stuff more familiar in popular lexicon.
I dont think i= t's helpful for users if we use the word "blocks".

"Confi= rmations" in a numeric context isn't correct, though. We're using to it because we've been using Bitcoin so long, but to the average person the= y would
expect it to mean something more than it is. If not referring= to blocks, then
perhaps "witnessed N times"?

Why not call it "Cleari= ng" for transactions with < 6 confirmations and "Cleared" for >=3D 6= ?
 
The round ticker should be enough of= an indication of the progress.


= --Boundary_(ID_JkWD4sVo9JeP/LVwHEhalQ)-- --Boundary_(ID_PDmc9IuD8uhb1Y4RrYR6tA)--