summaryrefslogtreecommitdiff
path: root/d9/8dd346b5e90c458685d06b2054dcf10f8faaa4
blob: 397cd429bdad60cd9b398b0eac7f64f5c021168d (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gavinandresen@gmail.com>) id 1WmTR3-0000Gq-FS
	for bitcoin-development@lists.sourceforge.net;
	Mon, 19 May 2014 19:41:21 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.213.53 as permitted sender)
	client-ip=209.85.213.53; envelope-from=gavinandresen@gmail.com;
	helo=mail-yh0-f53.google.com; 
Received: from mail-yh0-f53.google.com ([209.85.213.53])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WmTR2-0006GB-N6
	for bitcoin-development@lists.sourceforge.net;
	Mon, 19 May 2014 19:41:21 +0000
Received: by mail-yh0-f53.google.com with SMTP id i57so7214522yha.26
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 19 May 2014 12:41:15 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.236.170.37 with SMTP id o25mr7471435yhl.145.1400528475147;
	Mon, 19 May 2014 12:41:15 -0700 (PDT)
Received: by 10.170.188.77 with HTTP; Mon, 19 May 2014 12:41:15 -0700 (PDT)
Date: Mon, 19 May 2014 15:41:15 -0400
Message-ID: <CABsx9T2=nE1c-WOGnQiBqfFQqM0qtPiCcBsWN8pew6JhdpBNOA@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Justus Ranvier <justusranvier@gmail.com>
Content-Type: multipart/alternative; boundary=20cf302ef82a4255e204f9c5f2b9
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(gavinandresen[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WmTR2-0006GB-N6
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Working on social contracts (was: Paper
	Currency)
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 19 May 2014 19:41:21 -0000

--20cf302ef82a4255e204f9c5f2b9
Content-Type: text/plain; charset=UTF-8

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

--20cf302ef82a4255e204f9c5f2b9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On M=
on, May 19, 2014 at 2:20 PM, Justus Ranvier <span dir=3D"ltr">&lt;<a href=
=3D"mailto:justusranvier@gmail.com" target=3D"_blank">justusranvier@gmail.c=
om</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D""><br>
</div>You and Gavin could do a lot better by working on a Bitcoin social<br=
>
contract - a promise of what features will *never* be added (or taken<br>
away) from Bitcoin, because despite what you say it&#39;s not acceptable<br=
>
to propose anything at all.<br></blockquote><div><br></div><div>Now I&#39;m=
 really confused.</div><div><br></div><div>Why would Mike or I have the aut=
hority to write a &quot;social contract&quot; to promise anything about fut=
ure-Bitcoin?</div>
<div><br></div><div>I thought the only &quot;social contract&quot; was the =
decentralized one we have already-- if you don&#39;t like something about t=
he code, then don&#39;t download and run it. Or fork it if you&#39;re able.=
</div>
<div><br></div><div>As the person who started this mailing list, I DO feel =
like I have the authority to enforce a social contract of &quot;no trolling=
 or flaming or name-calling&quot; here. I&#39;d very much like to delegate =
that authority, though; ideally to some software algorithm that automatical=
ly censors topics or people who don&#39;t contribute to a productive discus=
sion.</div>
<div><br></div><div>PS: speaking of productive discussion...=C2=A0</div><di=
v>... please change the Subject line when the topic wanders.</div></div><di=
v><br></div>-- <br>--<br>Gavin Andresen<br>
</div><div class=3D"gmail_extra"><br></div></div>

--20cf302ef82a4255e204f9c5f2b9--