public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: hozer@hozed.org
To: muyuu <muyuubyou@gmail.com>,
	"cypherpunks@cpunks.org Bitcoin Protocol Discussion"
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Requirement for pseudonymous BIP submissions
Date: Fri, 24 Mar 2017 02:18:45 +0000	[thread overview]
Message-ID: <20170324021845.GC23538@hostname.unassigned> (raw)
In-Reply-To: <CADWuND34HbsF_e3Ob0bBPCzacsWrsfPjLzawwFd8KxcCoLDFSw@mail.gmail.com>

On Sun, Mar 19, 2017 at 11:43:12PM +0000, muyuu via bitcoin-dev wrote:
> If this was in place I would contribute more and I wouldn't have to create
> throw-away accounts.
> 
> This is not a space where you want to be a recognisable target.
> 
> Today, BitFury's CEO threatened to sue developers if they didn't kowtow to
> his demands to leave the PoW alone. This is unacceptable. Decisions have to
> be made on merit and the interest of the project, and nothing else.
> 
> This is very important and needs to be given priority. Most Core developers
> and all the main ones except Satoshi have built a public persona, either
> for ego or for practical monetary reasons. Obviously there's academia where
> everything is about plastering your name as much as possible and getting
> cited. So it's understood. Although I understand the difficulty of getting
> funded and getting trusted without a face, there needs to be an outlet so
> people can interact and contribute in a proper cypherpunk way.
> 
> Also, GitHub is quite anti-privacy. So I recommend not reusing personal
> accounts from work.
> 
> -muyuu

I quite agree, and I would add that sometimes making yourself
recognisable is far more important that merit.

If we are really going to go for merit, then we probably need to go
all the way back to examine why is it developers and academics think
they need to have money to make code or reputation to do research.

The best code I've written is stuff I've given away for free, although
sometimes I'm able to leverage being recognized for having written 
something into getting paid to write more code. The best research
I've done has been self-funded, when I did not subconsciously have
a funding agent I was trying to please with the outcome of the 
research.

We need a safe space for merit, how about http://gplspace.org/


  reply	other threads:[~2017-03-24  2:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-19 23:43 [bitcoin-dev] Requirement for pseudonymous BIP submissions muyuu
2017-03-24  2:18 ` hozer [this message]
     [not found]   ` <CAGL6+mEceO2D2ueeVgv20r5p6tsofMLSTN1ExWfGysJHuM5XfA@mail.gmail.com>
2017-03-28  1:31     ` Troy Benjegerdes
     [not found] <mailman.29.1489924803.11420.bitcoin-dev@lists.linuxfoundation.org>
2017-03-19 21:17 ` Steve Davis
  -- strict thread matches above, loose matches on Subject: below --
2017-03-18 15:23 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

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=20170324021845.GC23538@hostname.unassigned \
    --to=hozer@hozed.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=muyuubyou@gmail.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