public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd.org>
To: Staf Verhaegen <staf@stafverhaegen.be>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [Pre-BIP] Community Consensus Voting System
Date: Tue, 14 Feb 2017 07:33:17 -0500	[thread overview]
Message-ID: <20170214123317.GA8613@savin.petertodd.org> (raw)
In-Reply-To: <1486828666.21100.115.camel@stafverhaegen.be>

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

On Sat, Feb 11, 2017 at 04:57:46PM +0100, Staf Verhaegen via bitcoin-dev wrote:
> Chris Priest via bitcoin-dev schreef op vr 03-02-2017 om 16:57 [-0800]:
> > Personally I think once the blocksize arguments are solved, there will
> > be no more contentious changes for this voting system to deal with.
> > What other contentious issues have come up in the past 3 years or so
> > that wasn't blocksize/scaling related? Do other protocols like TCP/IP
> > and the HTTP protocol have developers arguing every day over issues no
> > one can agree on?
> 
> Yes, DRM for example.

...and note how, like blocksize, the roots of the DRM argument at W3C aren't a
technical disagreement, but rather a political disagreement.

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

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

  reply	other threads:[~2017-02-14 12:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02 19:39 [bitcoin-dev] [Pre-BIP] Community Consensus Voting System t. khan
2017-02-02 23:19 ` David Vorick
2017-02-03  0:24 ` Luke Dashjr
2017-02-03  1:32   ` Dave Scotese
2017-02-03 16:19     ` alp alp
2017-02-03 18:20       ` t. khan
2017-02-03 19:22         ` alp alp
2017-02-04 21:23           ` t. khan
2017-02-04  0:57         ` Chris Priest
2017-02-11 15:57           ` Staf Verhaegen
2017-02-14 12:33             ` Peter Todd [this message]
2017-02-04 22:02   ` t. khan

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=20170214123317.GA8613@savin.petertodd.org \
    --to=pete@petertodd.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=staf@stafverhaegen.be \
    /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