public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tom Zander <tomz@freedommail.ch>
To: bitcoin-dev@lists.linuxfoundation.org,
	Chris Stewart <chris@suredbits.com>
Subject: Re: [bitcoin-dev] Requirement for pseudonymous BIP submissions
Date: Wed, 29 Mar 2017 10:49:38 +0200	[thread overview]
Message-ID: <2003815.trufugliNn@strawberry> (raw)
In-Reply-To: <CAGL6+mEnGNdAggHZs=ZM_QHbts63exE1ydstK+w-gUnm=4JLTA@mail.gmail.com>

On Saturday, 18 March 2017 16:23:16 CEST Chris Stewart via bitcoin-dev 
wrote:
> As everyone in the Bitcoin space knows, there is a massive scaling debate
> going on. One side wants to increase the block size via segwit, while the
> other side wants to increase via hard fork. I have strong opinions on the
> topic but I won’t discuss them here. The point of the matter is we are
> seeing the politicization of protocol level changes.

I agree with your assessment, the sides are political and picking sides 
makes people a target.
For that reason I know that many companies are not picking sides, we’ve seen 
some bad stuff happen to companies that did.

I’m not convnced it makes sense to use anonymous, but provable, identities 
is the way to solve this. Though.

I also don’t believe people are rejecting proposals purely based on the 
name. What I see is that pratically all proposals are ignored for the time 
being becaues we can’t make any changes anyway until we have made a protocol 
upgrade and came out stronger.
I do agree that bips are seen politically, but not based on the person that 
suggests them, but more based on the content being useful for their 
political side.

I am not entirely against pseudonymous submissions, but in that case I think 
it should be carried by a well known member of the Bitcoin community.

This raises the bar somewhat to a point where you have to convince someone 
that is already publicly known to propose it with you.
-- 
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel


  parent reply	other threads:[~2017-03-29  8:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-18 15:23 [bitcoin-dev] Requirement for pseudonymous BIP submissions Chris Stewart
2017-03-18 16:57 ` Andrew Johnson
2017-03-18 17:35   ` Chris Stewart
2017-03-18 19:15 ` Luke Dashjr
2017-03-24  2:30   ` Troy Benjegerdes
2017-03-29  8:49 ` Tom Zander [this message]
     [not found] <mailman.29.1489924803.11420.bitcoin-dev@lists.linuxfoundation.org>
2017-03-19 21:17 ` Steve Davis
2017-03-19 23:43 muyuu
2017-03-24  2:18 ` hozer
     [not found]   ` <CAGL6+mEceO2D2ueeVgv20r5p6tsofMLSTN1ExWfGysJHuM5XfA@mail.gmail.com>
2017-03-28  1:31     ` Troy Benjegerdes

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=2003815.trufugliNn@strawberry \
    --to=tomz@freedommail.ch \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=chris@suredbits.com \
    /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