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
130
131
132
133
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <btcdrak@gmail.com>) id 1Y5ZDL-00070t-LN
for bitcoin-development@lists.sourceforge.net;
Mon, 29 Dec 2014 12:14:23 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.48 as permitted sender)
client-ip=74.125.82.48; envelope-from=btcdrak@gmail.com;
helo=mail-wg0-f48.google.com;
Received: from mail-wg0-f48.google.com ([74.125.82.48])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Y5ZD5-0001Gi-P9
for bitcoin-development@lists.sourceforge.net;
Mon, 29 Dec 2014 12:14:23 +0000
Received: by mail-wg0-f48.google.com with SMTP id y19so18746504wgg.7
for <bitcoin-development@lists.sourceforge.net>;
Mon, 29 Dec 2014 04:14:01 -0800 (PST)
X-Received: by 10.194.238.104 with SMTP id vj8mr20327686wjc.107.1419855241718;
Mon, 29 Dec 2014 04:14:01 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.25.130 with HTTP; Mon, 29 Dec 2014 04:13:41 -0800 (PST)
In-Reply-To: <CANEZrP0GsuiCF4oHGnTnVXwUsc0dNBOTtusr_CFn+29SxYYwHw@mail.gmail.com>
References: <CANEZrP1tGYOsShk5Z91_JwH7E0pX8WcyT_-ZBkrWBqZAyrcd1A@mail.gmail.com>
<3685166.ROb67lzbMM@coldstorage>
<CANEZrP0GsuiCF4oHGnTnVXwUsc0dNBOTtusr_CFn+29SxYYwHw@mail.gmail.com>
From: Btc Drak <btcdrak@gmail.com>
Date: Mon, 29 Dec 2014 12:13:41 +0000
Message-ID: <CADJgMzsL26G1YRK+gBfHx-=XOKVDQjj0=sdF-j3dur1Zux9Oew@mail.gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=089e013d141a50b043050b59cfbb
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.0 HK_RANDOM_FROM From username looks random
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.6 HK_RANDOM_ENVFROM Envelope sender username looks random
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(btcdrak[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: 1Y5ZD5-0001Gi-P9
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Cartographer
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, 29 Dec 2014 12:14:23 -0000
--089e013d141a50b043050b59cfbb
Content-Type: text/plain; charset=UTF-8
Mike,
In all seriousness, are you on the payroll of the NSA or similar to
repeatedly attempt to introduce privacy leaks[1] and weaknesses[2] into the
ecosystem not to mention logical fallacies like ad hominem attacks;
disruption[3] and FUD[4]?
Why do you answer objections by hand waving and misdirection as opposed to
sound technical reasoning? Remember how hand waving ended for you the last
time with your p2p getutxo pull-request[5] and the public flogging the
ensued because you refused to accept your implementation was not only
flawed but critically vulnerable to attack[6].
Given your intelligence, education and experience, it would seem logical
that your behaviour is not random or irrational, but in fact calculated and
planned.
references:
[1]
http://www.reddit.com/r/Bitcoin/comments/2byqz0/mike_hearn_proposes_to_build_vulnerable/
[2]
https://www.reddit.com/r/Bitcoin/comments/1qmbtu/mike_hearn_chair_of_the_bitcoin_foundations_law/
[3]
http://www.reddit.com/r/Bitcoin/comments/28zts3/mike_hearn_interview_quotes_progress_on_the/
[4] https://www.youtube.com/watch?v=iMIzMVABFxQ
[5] https://github.com/bitcoin/bitcoin/pull/4351
[6]
http://www.reddit.com/r/Bitcoin/comments/2eq8gi/getutxos_a_convenient_way_to_crash_bitcoind/
--089e013d141a50b043050b59cfbb
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=
>Mike,</div><div><br></div><div>In all seriousness, are you on the payroll =
of the NSA or similar to repeatedly attempt to introduce privacy leaks[1] a=
nd weaknesses[2] into the ecosystem not to mention logical fallacies like a=
d hominem attacks; disruption[3] and FUD[4]?=C2=A0</div><div><br></div><div=
>Why do you answer objections by hand waving and misdirection as opposed to=
sound technical reasoning? Remember how hand waving ended for you the last=
time with your p2p getutxo pull-request[5] and the public flogging the ens=
ued because you refused to accept your implementation was not only flawed b=
ut critically vulnerable to attack[6].<br></div><div><br></div><div>Given y=
our intelligence, education and experience, it would seem logical that your=
behaviour is not random or irrational, but in fact calculated and planned.=
</div><div><br></div><div>references:</div><div>[1]=C2=A0<a href=3D"http://=
www.reddit.com/r/Bitcoin/comments/2byqz0/mike_hearn_proposes_to_build_vulne=
rable/" target=3D"_blank">http://www.reddit.com/r/Bitcoin/comments/2byqz0/m=
ike_hearn_proposes_to_build_vulnerable/</a><br></div><div>[2]=C2=A0<a href=
=3D"https://www.reddit.com/r/Bitcoin/comments/1qmbtu/mike_hearn_chair_of_th=
e_bitcoin_foundations_law/" target=3D"_blank">https://www.reddit.com/r/Bitc=
oin/comments/1qmbtu/mike_hearn_chair_of_the_bitcoin_foundations_law/</a></d=
iv><div>[3]=C2=A0<a href=3D"http://www.reddit.com/r/Bitcoin/comments/28zts3=
/mike_hearn_interview_quotes_progress_on_the/" target=3D"_blank">http://www=
.reddit.com/r/Bitcoin/comments/28zts3/mike_hearn_interview_quotes_progress_=
on_the/</a></div><div>[4]=C2=A0<a href=3D"https://www.youtube.com/watch?v=
=3DiMIzMVABFxQ">https://www.youtube.com/watch?v=3DiMIzMVABFxQ</a></div><div=
>[5]=C2=A0<a href=3D"https://github.com/bitcoin/bitcoin/pull/4351" target=
=3D"_blank">https://github.com/bitcoin/bitcoin/pull/4351</a></div><div>[6]=
=C2=A0<a href=3D"http://www.reddit.com/r/Bitcoin/comments/2eq8gi/getutxos_a=
_convenient_way_to_crash_bitcoind/">http://www.reddit.com/r/Bitcoin/comment=
s/2eq8gi/getutxos_a_convenient_way_to_crash_bitcoind/</a>=C2=A0</div><div><=
br></div></div></div></div>
--089e013d141a50b043050b59cfbb--
|
