From: Milly Bitcoin <milly@bitcoins•info>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] improving development model (Re: Concerns Regarding Threats by a Developer to Remove Commit Access from Other Developers
Date: Fri, 19 Jun 2015 12:05:38 -0400 [thread overview]
Message-ID: <55843DD2.3080006@bitcoins.info> (raw)
In-Reply-To: <CALqxMTFx6DF0Re+pCwB1AjYo6eYuKtX1cqUpo=wXmHSOsN74dQ@mail.gmail.com>
>- Did you accept payment from companies to lobby for 20MB blocks? Do
you consider that something appropriate to publicly disclose if so? Do
you consider that user rights should come above or below company
interests in Bitcoin? FWIW on pondering that last question "should user
rights come above or below company interests" I think my view of the
guiding principle is starkly clear to me: that user rights should be the
primary thing to optimise for. Businesses are providing service to
users, their interests are secondary in so far as if they are enabled to
provide better service thats good. Bitcoin is a user p2p currency, with
a social contract and a strong user ethos. Importing and forcing company
interests would likely be the start of a slippery slope towards an end
to Bitcoin.
I always thought is was the exact opposite. I thought it was expected
that the only incentive for developers (other than increasing the value
of coins they hold) is to lobby for changes that will benefit the
companies that fund them. That is the only way you are going to get
more full time developers on board. It focuses their efforts on
products and services people want rather than some sort philosophical
agenda that may be unrealistic. The notion that large numbers of
volunteers will do all this work at little or no pay to improve user
experience is not a realistic long term plan. I also think it is
incorrect to assume some kind of "social contract" and "strong user
ethos." While many early users are like that I think most potential
users of Bitcoin don't think that way.
Russ
prev parent reply other threads:[~2015-06-19 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 9:22 Dr Adam Back
2015-06-19 10:45 ` Dr Adam Back
2015-06-19 11:35 ` Bryan Bishop
2015-06-19 12:02 ` Eric Lombrozo
2015-06-19 12:02 ` Eric Lombrozo
2015-06-19 12:48 ` Marcel Jamin
2015-06-19 12:49 ` Eric Lombrozo
2015-06-19 13:43 ` Mike Hearn
2015-06-20 2:59 ` Tom Harding
2015-06-19 16:05 ` Milly Bitcoin [this message]
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=55843DD2.3080006@bitcoins.info \
--to=milly@bitcoins$(echo .)info \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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