From: Gavin Andresen <gavinandresen@gmail•com>
To: Justus Ranvier <justusranvier@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Working on social contracts (was: Paper Currency)
Date: Mon, 19 May 2014 15:41:15 -0400 [thread overview]
Message-ID: <CABsx9T2=nE1c-WOGnQiBqfFQqM0qtPiCcBsWN8pew6JhdpBNOA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]
On Mon, May 19, 2014 at 2:20 PM, Justus Ranvier <justusranvier@gmail•com>wrote:
>
> You and Gavin could do a lot better by working on a Bitcoin social
> contract - a promise of what features will *never* be added (or taken
> away) from Bitcoin, because despite what you say it's not acceptable
> to propose anything at all.
>
Now I'm really confused.
Why would Mike or I have the authority to write a "social contract" to
promise anything about future-Bitcoin?
I thought the only "social contract" was the decentralized one we have
already-- if you don't like something about the code, then don't download
and run it. Or fork it if you're able.
As the person who started this mailing list, I DO feel like I have the
authority to enforce a social contract of "no trolling or flaming or
name-calling" here. I'd very much like to delegate that authority, though;
ideally to some software algorithm that automatically censors topics or
people who don't contribute to a productive discussion.
PS: speaking of productive discussion...
... please change the Subject line when the topic wanders.
--
--
Gavin Andresen
[-- Attachment #2: Type: text/html, Size: 1700 bytes --]
next reply other threads:[~2014-05-19 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 19:41 Gavin Andresen [this message]
2014-05-19 20:01 ` Justus Ranvier
2014-05-19 20:06 ` Gavin Andresen
2014-05-19 20:06 ` Mike Hearn
2014-05-19 20:13 ` Justus Ranvier
2014-05-19 21:07 ` Gregory Maxwell
2014-05-19 21:18 ` Justus Ranvier
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='CABsx9T2=nE1c-WOGnQiBqfFQqM0qtPiCcBsWN8pew6JhdpBNOA@mail.gmail.com' \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=justusranvier@gmail$(echo .)com \
/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