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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
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 1WST9H-0006HF-B5
for bitcoin-development@lists.sourceforge.net;
Tue, 25 Mar 2014 15:20:19 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.41 as permitted sender)
client-ip=209.85.219.41; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f41.google.com;
Received: from mail-oa0-f41.google.com ([209.85.219.41])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WST98-0008Cf-MQ
for bitcoin-development@lists.sourceforge.net;
Tue, 25 Mar 2014 15:20:19 +0000
Received: by mail-oa0-f41.google.com with SMTP id j17so757237oag.0
for <bitcoin-development@lists.sourceforge.net>;
Tue, 25 Mar 2014 08:20:05 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.229.228 with SMTP id st4mr62766291oec.16.1395760805350;
Tue, 25 Mar 2014 08:20:05 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.71.231 with HTTP; Tue, 25 Mar 2014 08:20:05 -0700 (PDT)
In-Reply-To: <20140325134918.GB7929@savin>
References: <20140322084702.GA13436@savin> <20140322150836.GG3180@nl.grid.coop>
<20140322190825.GB6047@savin> <532DE7E6.4050304@monetize.io>
<20140325122851.GA9818@savin>
<CABsx9T149f9of9+sYMFazAxtRi=ZJrpA1B41buERD3+j7NGKmg@mail.gmail.com>
<20140325134918.GB7929@savin>
Date: Tue, 25 Mar 2014 16:20:05 +0100
X-Google-Sender-Auth: Cw4aFyZa0K9nZlSYskK4bg70DB0
Message-ID: <CANEZrP16pR0pJmZaD5JgCHf9WKjcMAxyuNz2iieuOE6G9E0KkA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Peter Todd <pete@petertodd.org>
Content-Type: multipart/alternative; boundary=001a11362fb0fe986b04f56fe292
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: 1WST98-0008Cf-MQ
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
Gavin Andresen <gavin@bitcoinfoundation.org>
Subject: Re: [Bitcoin-development] Tree-chains preliminary summary
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: Tue, 25 Mar 2014 15:20:19 -0000
--001a11362fb0fe986b04f56fe292
Content-Type: text/plain; charset=UTF-8
A few months ago I had a conversation with an executive at a Bitcoin
company, and I suggested their developers should get involved with the
development list. I was told that they are all subscribed but refuse to
post. Puzzled, I asked why, maybe the process isn't clear or we didn't talk
about what they were interested in? No, it's because in that executives
words "They see how Peter Todd shoots people down in flames and want
nothing to do with that".
Peter, you were named explicitly as the source of the problem. Your
immediate knee-jerk reaction to anyone who disagrees with you is making
this forum aggressive and ugly - it puts other people off from
contributing. For what it's worth, if I were the moderator of this list I
would have banned you a long time ago because I value a friendly atmosphere
more than your "insights", which are often deeply suspect (as in this case).
Besides, ground up redesigns of Bitcoin like what you propose are more
appropriate for bitcointalk. So please take it there.
--001a11362fb0fe986b04f56fe292
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra">A few months ago I had a conver=
sation with an executive at a Bitcoin company, and I suggested their develo=
pers should get involved with the development list. I was told that they ar=
e all subscribed but refuse to post. Puzzled, I asked why, maybe the proces=
s isn't clear or we didn't talk about what they were interested in?=
No, it's because in that executives words "They see how Peter Tod=
d shoots people down in flames and want nothing to do with that".=C2=
=A0</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Peter, you =
were named explicitly as the source of the problem. Your immediate knee-jer=
k reaction to anyone who disagrees with you is making this forum aggressive=
and ugly - it puts other people off from contributing. For what it's w=
orth, if I were the moderator of this list I would have banned you a long t=
ime ago because I value a friendly atmosphere more than your "insights=
", which are often deeply suspect (as in this case).</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Besides, gr=
ound up redesigns of Bitcoin like what you propose are more appropriate for=
bitcointalk. So please take it there.</div></div>
--001a11362fb0fe986b04f56fe292--
|
