public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd.org>
To: Luke-Jr <luke@dashjr.org>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] 0.8.1 ideas
Date: Wed, 13 Mar 2013 12:04:21 -0400	[thread overview]
Message-ID: <20130313160421.GA23566@savin> (raw)
In-Reply-To: <201303131526.16406.luke@dashjr.org>

[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]

On Wed, Mar 13, 2013 at 03:26:14PM +0000, Luke-Jr wrote:
> On Wednesday, March 13, 2013 3:18:36 PM Gregory Maxwell wrote:
> > On Wed, Mar 13, 2013 at 8:05 AM, Peter Todd <pete@petertodd.org> wrote:
> > > If we're going to consider doing this, at minimum we need to also
> > 
> > I beg people to not derail discussion about fixing things with
> > discussion of other controversial changes.
> 
> I figured 2 MB in 2-3 years was fairly uncontroversial.
> If not, let's scrap that idea for now.

The very statement that we're willing to increase the blocksize as our
solution to increased transaction volume rather go down the path of
off-chain transactions is incredibly controversial.

Fuck it, I'll make this public: I've had at least one person who went to
the trouble of finding my personal phone number just so they could leave
a few text messages saying I was going to do serious harm to Bitcoin. At
the same time I've also had a few people asking questions along the line
of had started and/or was considering starting a formal group opposing
the blocksize increase. I even got a significant anonymous donation a
few weeks ago. (rather fittingly this was done by emailing me an
easywallet URL from a throwaway account)

It's not just forum trolls who care about the issue, even if they make
the most noise about it.

-- 
'peter'[:-1]@petertodd.org

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-03-13 16:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13 12:56 [Bitcoin-development] 0.8.1 ideas Luke-Jr
2013-03-13 13:14 ` Gregory Maxwell
2013-03-13 15:05 ` Peter Todd
2013-03-13 15:18   ` Gregory Maxwell
2013-03-13 15:26     ` Luke-Jr
2013-03-13 16:04       ` Peter Todd [this message]
2013-03-13 17:41 ` Mark Friedenbach
2013-03-13 17:58   ` Pieter Wuille
2013-03-13 18:27     ` Mark Friedenbach
2013-03-13 18:35       ` slush
2013-03-13 18:38       ` Pieter Wuille
2013-03-13 19:30       ` Gregory Maxwell
     [not found]         ` <16B6728E-4220-4DA6-B740-FA38A7C19CCB@thelibertyportal.com>
2013-03-13 20:24           ` Gregory Maxwell
2013-03-13 20:18       ` Luke-Jr
2013-03-13 18:04   ` Luke-Jr
2013-03-13 21:06 ` Andy Parkins
2013-03-13 21:14   ` Luke-Jr
2013-03-13 21:22     ` Roy Badami
2013-03-13 21:27       ` Gregory Maxwell
2013-03-13 21:36         ` Roy Badami
2013-03-14  0:18           ` Cameron Garnham
2013-03-15 17:06             ` Benjamin Lindner
2013-03-15 19:23               ` Luke-Jr
2013-03-15 19:52               ` Gregory Maxwell

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=20130313160421.GA23566@savin \
    --to=pete@petertodd.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=luke@dashjr.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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