From: Peter Todd <pete@petertodd•org>
To: Dave Scotese <dscotese@litmocracy•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP 100 specification
Date: Thu, 3 Sep 2015 23:50:45 -0400 [thread overview]
Message-ID: <20150904035045.GA9821@muck> (raw)
In-Reply-To: <CAGLBAhfUky0=5KoUcNxUV0N-jayHAx1Y+Ri3GdvrtMNSZA8tjg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 648 bytes --]
On Thu, Sep 03, 2015 at 01:34:54PM -0700, Dave Scotese via bitcoin-dev wrote:
> 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.
The IEC standard is to use the prefix MiB for 2^20 bytes:
https://en.wikipedia.org/wiki/Binary_prefix
--
'peter'[:-1]@petertodd.org
000000000000000010f9e95aff6454fedb9d0a4b92a4108e9449c507936f9f18
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
prev parent reply other threads:[~2015-09-04 3:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 3:33 Jeff Garzik
2015-09-03 4:45 ` Dave Scotese
2015-09-03 7:57 ` jl2012
2015-09-03 11:20 ` Btc Drak
2015-09-03 14:34 ` Jeff Garzik
2015-09-03 15:58 ` Btc Drak
2015-09-03 16:13 ` Jorge Timón
2015-09-03 11:59 ` Tier Nolan
2015-09-03 16:32 ` jl2012
2015-09-03 16:35 ` Jeff Garzik
2015-09-03 17:32 ` Btc Drak
2015-09-03 17:52 ` Peter Todd
2015-09-04 7:53 ` Andy Chase
2015-09-04 15:37 ` Simon Liu
2015-09-04 15:40 ` Btc Drak
2015-09-03 14:35 ` Jeff Garzik
2015-09-03 19:40 ` Simon Liu
2015-09-03 20:15 ` Oliver Petruzel
2015-09-03 20:34 ` Dave Scotese
2015-09-04 3:50 ` Peter Todd [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150904035045.GA9821@muck \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=dscotese@litmocracy$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox