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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1WmMZl-0003eP-H0
for bitcoin-development@lists.sourceforge.net;
Mon, 19 May 2014 12:21:53 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.53 as permitted sender)
client-ip=209.85.219.53; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f53.google.com;
Received: from mail-oa0-f53.google.com ([209.85.219.53])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WmMZk-0007ka-Gd
for bitcoin-development@lists.sourceforge.net;
Mon, 19 May 2014 12:21:53 +0000
Received: by mail-oa0-f53.google.com with SMTP id m1so6160376oag.12
for <bitcoin-development@lists.sourceforge.net>;
Mon, 19 May 2014 05:21:47 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.44.165 with SMTP id f5mr14498424oem.38.1400502107076;
Mon, 19 May 2014 05:21:47 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.71.162 with HTTP; Mon, 19 May 2014 05:21:47 -0700 (PDT)
In-Reply-To: <BAY173-W1475F72C70BC089A82C20FCC300@phx.gbl>
References: <BAY173-W1475F72C70BC089A82C20FCC300@phx.gbl>
Date: Mon, 19 May 2014 14:21:47 +0200
X-Google-Sender-Auth: fQUVXAgcWXBom4ShMiMaIhIRCkk
Message-ID: <CANEZrP27wSZ=aFdW5Nw1gGqemE4GeLbfTS5=DD5uX+fsTfpF3g@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Jerry Felix <jerfelix@hotmail.com>
Content-Type: multipart/alternative; boundary=001a11334484997dc004f9bfce09
X-Spam-Score: -0.5 (/)
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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1WmMZk-0007ka-Gd
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] 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 12:21:53 -0000
--001a11334484997dc004f9bfce09
Content-Type: text/plain; charset=UTF-8
> Submitted with humility and some fear of getting laughed out of here...
>
Off topic aside, a bunch of us have lately started to think about the
atmosphere on this list and how to improve it. Nobody should have to fear
getting flamed or laughed at for proposing ideas, even if they turn out to
be silly ones. Gavin talked about this in his Bitcoin 2014 keynote and
asked for someone to solve the forum trolling problem.
I don't know if there are any silver bullets per se, but:
1) Please do keep ideas coming. It's easy to mute threads in any good mail
client for people who don't care. If anyone gets too aggressive, the rest
of us will remind them that this is unacceptable.
2) If you're willing to become a list moderator, please get in touch. Gavin
and I are looking for neutral people who are willing to keep up with this
list and help ensure the debate is civilised. Ideally moderation is not
necessary, but that's what we tried so far and we keep getting consistent
feedback from lots of people that it's not working.
--001a11334484997dc004f9bfce09
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"><div=
>=C2=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div><div dir=3D"ltr">Submi=
tted with humility and some fear of getting laughed out of here...</div>
</div></blockquote><div><br></div><div>Off topic aside, a bunch of us have =
lately started to think about the atmosphere on this list and how to improv=
e it. Nobody should have to fear getting flamed or laughed at for proposing=
ideas, even if they turn out to be silly ones. Gavin talked about this in =
his Bitcoin 2014 keynote and asked for someone to solve the forum trolling =
problem.</div>
<div><br></div><div>I don't know if there are any silver bullets per se=
, but:</div><div><br></div><div>1) Please do keep ideas coming. It's ea=
sy to mute threads in any good mail client for people who don't care. I=
f anyone gets too aggressive, the rest of us will remind them that this is =
unacceptable.</div>
<div><br></div><div>2) If you're willing to become a list moderator, pl=
ease get in touch. Gavin and I are looking for neutral people who are willi=
ng to keep up with this list and help ensure the debate is civilised. Ideal=
ly moderation is not necessary, but that's what we tried so far and we =
keep getting consistent feedback from lots of people that it's not work=
ing.</div>
<div><br></div><div><br></div></div></div></div>
--001a11334484997dc004f9bfce09--
|
