From: Peter Todd <pete@petertodd•org>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] NODE_BLOOM BIP
Date: Sun, 18 Aug 2013 18:59:30 -0400 [thread overview]
Message-ID: <20130818225930.GA23974@savin> (raw)
In-Reply-To: <CANEZrP2jONtRJ6oF1YqKJB9nm1HcMkfz_yzeNshEWqD-5fdNiA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 639 bytes --]
On Mon, Aug 19, 2013 at 12:00:23AM +0200, Mike Hearn wrote:
> The original Bloom filtering spec did not make this feature optional for
> the same reason gzip isn't an optional part of the PNG specification. I see
> no reason to revisit that. It's definitely not the case that making every
> possible feature optional is smart design, often it's the opposite.
Bloom filtering isn't lossless so to speak.
A better analogy would be making re-sharing an optinal part of the
BitTorrent specification, and then expecting that the majority of users
would never upload data to peers that needed it.
--
'peter'[:-1]@petertodd.org
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
prev parent reply other threads:[~2013-08-18 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-18 2:59 Peter Todd
2013-08-18 22:00 ` Mike Hearn
2013-08-18 22:22 ` Gavin Andresen
2013-08-18 23:11 ` Peter Todd
2013-08-18 22:59 ` 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=20130818225930.GA23974@savin \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/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