From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 8DA85D28 for ; Thu, 3 Sep 2015 20:34:55 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-ob0-f180.google.com (mail-ob0-f180.google.com [209.85.214.180]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 30BC617D for ; Thu, 3 Sep 2015 20:34:55 +0000 (UTC) Received: by obbbh8 with SMTP id bh8so1157480obb.0 for ; Thu, 03 Sep 2015 13:34:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=QXCASksIcu788X6qJ4/qNq423st/kHZ9VQ0DYx9a9dk=; b=k2GNGQS+Db7UbxGMyPnazgvlrJoVFHf0FuqEesBN+L544a+RBUv0muN8XoTLC7kzVA b3YHYoqh5ROQww63hKU9GPypy/y5Wnj2mgHyVQtv+M0io7cgo8r3cbge+6fvw3tkeA9B JVuoSJAnVCKT71/0XSY4jQNUxJ/R0sY6j1tITk7ehqdwh15JlZY+6w9Kw99DR0cdlr+U kiY6UWkKGIWGHML0/Ax6Frd3VjA6Bf5ceUelgY6BfOB0IZWO/vrkpuatuOOXFRcOTW3j 3ISWPOI3EXEMKszrdEDJnq47XI5+nja2Ux7KDf1VhTvQOBEmxLnltpO1qfkkMRbuxdKO Qp3g== MIME-Version: 1.0 X-Received: by 10.182.28.105 with SMTP id a9mr14722395obh.51.1441312494555; Thu, 03 Sep 2015 13:34:54 -0700 (PDT) Sender: dscotese@gmail.com Received: by 10.202.201.2 with HTTP; Thu, 3 Sep 2015 13:34:54 -0700 (PDT) In-Reply-To: References: <55E8A246.7030102@bitcartel.com> Date: Thu, 3 Sep 2015 13:34:54 -0700 X-Google-Sender-Auth: OpUSfk3nM5CIzKqJFgNcbG6h2XA Message-ID: From: Dave Scotese To: Bitcoin Dev Content-Type: multipart/alternative; boundary=089e0149c2063f9622051eddb7a9 X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] BIP 100 specification X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Sep 2015 20:34:55 -0000 --089e0149c2063f9622051eddb7a9 Content-Type: text/plain; charset=UTF-8 I have seen "1M" mean 1,000,000 bytes as well as 1,048,576bytes and 1,024,000 bytes. I believe the best policy is to use "megabyte" to mean 2^20 (1,048,576) bytes. Kb always means 1024 bytes, even when a lot people round it, so I like the K spec best. I also see value in having human readable data. The spec should nail down these details. --089e0149c2063f9622051eddb7a9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I have seen "1M" mean 1,000,000 bytes as well as= 1,048,576bytes and 1,024,000 bytes.=C2=A0 I believe the best policy is to = use "megabyte" to mean 2^20 (1,048,576) bytes.=C2=A0 Kb always me= ans 1024 bytes, even when a lot people round it, so I like the K spec best.= =C2=A0 I also see value in having human readable data.=C2=A0 The spec shoul= d nail down these details.

--089e0149c2063f9622051eddb7a9--