From: Peter Todd <pete@petertodd•org>
To: "Jorge Timón" <jtimon@jtimon•cc>, bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP 102 - kick the can down the road to 2MB
Date: Tue, 21 Jul 2015 09:58:46 -0400 [thread overview]
Message-ID: <20150721135846.GB13429@savin.petertodd.org> (raw)
In-Reply-To: <20150721130412.GA4551@savin.petertodd.org>
[-- Attachment #1: Type: text/plain, Size: 2502 bytes --]
On Tue, Jul 21, 2015 at 09:04:12AM -0400, Peter Todd via bitcoin-dev wrote:
> For that reason I think BIP102 is extremely poorly designed. I can only
> conclude that Jeff Garzik is either deliberately trolling us and/or
> manipulating discussion with a badly designed proposal that he doesn't
> actually expect to be adopted verbatim, or is incompetent.
Expanding on that a bit:
On Tue, Jul 21, 2015 at 09:14:26PM +0800, Jeremy Rubin wrote:
> unsolicited feedback:
>
> I'd send a quick apology for this bit
>
> """
> For that reason I think BIP102 is extremely poorly designed. I can only
> conclude that Jeff Garzik is either deliberately trolling us and/or
> manipulating discussion with a badly designed proposal that he doesn't
> actually expect to be adopted verbatim, or is incompetent.
> """
>
> it's a little over the top.
>
> I think that Garzik is probably releasing it in reaction to the fact
> certain people are only looking at something with code attached.
>
> No need to call someone stupid for sharing a proposal... although it seems
> sketchy that he got a BIP # for this. You want to foster a less hostile
> community...
I don't agree with you at all.
This is a case where if Jeff doesn't understand that issue, he's
proposing changes that he's not competent enough to understand, and it'd
save us a lot of review effort if he left that discussion. Equally, Jeff
is in a position in the dev community where he should be that competent;
if he actually isn't it does a lot of good for the broader community to
change that opinion.
I personally *don't* think he's doing that, rather I believe he knows
full well it's a bad patch and is proposing it because he wants to push
discussion towards a solution. Often trolling the a audience with bad
patches is an effective way to motivate people to respond by writing
better ones; Jeff has told me he often does exactly that.
I think in this case we shouldn't do anything, so short-circuiting that
process by pointing out what he's doing publicly makes sense.
Re: BIP #'s, we explicitly have a policy of allocating them for stupid
ideas, to avoid having to be gatekeepers. Ironically that makes it
harder to get a BIP # if you know what you're doing, because Gregory
Maxwell will argue against you in private and delay actually allocating
one if he knows you should know better. :)
--
'peter'[:-1]@petertodd.org
00000000000000000d9cad4228c0396ff49c1de60f8ee155928eee22705f6619
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
next prev parent reply other threads:[~2015-07-21 13:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 15:55 Jeff Garzik
2015-07-17 16:11 ` Andrew
2015-07-17 16:12 ` Tier Nolan
2015-07-17 16:14 ` Tier Nolan
2015-07-17 17:57 ` Ross Nicoll
2015-07-17 19:06 ` Chris Wardell
2015-07-17 19:13 ` Ross Nicoll
2015-07-19 22:51 ` Ross Nicoll
2015-07-21 9:26 ` Jorge Timón
2015-07-21 13:04 ` Peter Todd
2015-07-21 13:58 ` Peter Todd [this message]
2015-07-22 15:51 ` Tom Harding
2015-07-22 17:02 ` Sriram Karra
2015-07-22 17:40 ` Sriram Karra
2015-07-22 17:43 ` Jeff Garzik
2015-07-22 22:30 ` Peter Todd
2015-07-23 5:39 ` jl2012
2015-07-22 17:00 ` jl2012
2015-07-21 22:05 ` Ross Nicoll
2015-07-23 11:24 ` Jorge Timón
2015-07-17 20:29 ` Luke Dashjr
2015-07-17 21:13 ` Angel Leon
2015-07-17 22:25 ` Tier Nolan
2015-07-18 9:22 ` Jorge Timón
2015-07-18 9:24 ` Jorge Timón
2015-07-24 8:52 ` Thomas Zander
2015-07-24 9:43 ` Slurms MacKenzie
2015-07-18 4:32 ` Venzen Khaosan
2015-07-17 22:40 Raystonn
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=20150721135846.GB13429@savin.petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jtimon@jtimon$(echo .)cc \
/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