public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Justus Ranvier <justusranvier@gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>,
	 Justus Ranvier <justusranvier@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Working on social contracts (was: Paper Currency)
Date: Mon, 19 May 2014 23:18:54 +0200	[thread overview]
Message-ID: <537A753E.60200@localhost.local> (raw)
In-Reply-To: <CAAS2fgQADU27NABcP1r52YTgDUy+PX7OZfT5H7XSsecjy1dmQg@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/19/2014 11:07 PM, Gregory Maxwell wrote:
> I promise that if bad people show up with a sufficient pointy gun
> that I'll do whatever they tell me to do. I'll make bad proposals,
> submit backdoors, and argue with querulous folks on mailing lists,
> diverting them from real development and review work, all as
> commanded. Maybe I'll try to sneak out a warning of some kind,
> maybe... but with my life or my families or friends lives on the
> line— probably not.
> 
> ... and I think that anyone who tells you otherwise probably just 
> hasn't really thought it through.  So what is the point of
> commitments like that?  People change, people go crazy, people are
> coerced. Crap happens, justifications are made, life goes on— or so
> we hope.

I presume you're familiar with the concept of a warrant canary, so
presumably you'd also see why public statements such as I was
discussing would be similarly useful.

Social contracts make it more difficult to hide coercion, which serves
no one except the attackers.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTenU+AAoJEMP3uyY4RQ21P1UH/2fvYa7Hfv53eXA0k9appRVI
8KWpH2D95zCo/s6kIeKZtmEzhFWFkKxOHwiHZbD5JokG+U/vUeR8p+SxF1/xUc1X
1tTNAjfAALz0/KzjPKmlMQCqM5vT4yumHsDusqPuzbPFnJnwFufrAW9vWu9OJacs
JEv4yoRGNZhR+eM8hCUkDfTtj7D8J3gMYyYds7K4kppiHN2UPRgZT6TCVyCRlThe
8w9MzYoTAf1WXPmzvSfPhzKMfNV9Y+tjt6ZV+KyLG1ZGLw2EDCxJR1O23QQE8IfK
53I2RgeFnvcdceoExSfYJj+kNpbPQ/WDVszswO5esoMWJ/E3j5PCBsLdGt+8e7I=
=BysA
-----END PGP SIGNATURE-----



      reply	other threads:[~2014-05-19 21:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-19 19:41 [Bitcoin-development] Working on social contracts (was: Paper Currency) Gavin Andresen
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 [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=537A753E.60200@localhost.local \
    --to=justusranvier@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=gmaxwell@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