summaryrefslogtreecommitdiff
path: root/b5/440a7f6e132c54069031df1d28df2fceccede6
blob: dde292d4d2fdcbc46f52250c194a1708d6526089 (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
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1Wmfd5-0003g1-Mm
	for bitcoin-development@lists.sourceforge.net;
	Tue, 20 May 2014 08:42:35 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.219.47 as permitted sender)
	client-ip=209.85.219.47; envelope-from=mh.in.england@gmail.com;
	helo=mail-oa0-f47.google.com; 
Received: from mail-oa0-f47.google.com ([209.85.219.47])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Wmfd4-0006Xo-Ah
	for bitcoin-development@lists.sourceforge.net;
	Tue, 20 May 2014 08:42:35 +0000
Received: by mail-oa0-f47.google.com with SMTP id i7so142064oag.34
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 20 May 2014 01:42:28 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.144.161 with SMTP id sn1mr1444564obb.82.1400575348742;
	Tue, 20 May 2014 01:42:28 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.71.162 with HTTP; Tue, 20 May 2014 01:42:28 -0700 (PDT)
Received: by 10.76.71.162 with HTTP; Tue, 20 May 2014 01:42:28 -0700 (PDT)
In-Reply-To: <trinity-1957ed0e-a607-47d7-803b-71c59af8eb89-1400573744536@3capp-mailcom-bs08>
References: <CANEZrP2rgiQHpekEpFviJ22QsiV+s-F2pqosaZOA5WrRtJx5pg@mail.gmail.com>
	<CANAnSg0ABVyRcSaO2aEcqO8qaj+JdxRN4z-hLE-EbESv2TMf2g@mail.gmail.com>
	<trinity-1957ed0e-a607-47d7-803b-71c59af8eb89-1400573744536@3capp-mailcom-bs08>
Date: Tue, 20 May 2014 10:42:28 +0200
X-Google-Sender-Auth: NERlcpX4a1JMPcCuLbk5gZ4oDgw
Message-ID: <CANEZrP2qRP3ayP5ognX4hz6JMG57A96NerX3+xBwi6WPcRcqiQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: bitcoingrant@gmx.com
Content-Type: multipart/alternative; boundary=089e0158ac7824a1a504f9d0dc16
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: 1Wmfd4-0006Xo-Ah
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Why are we bleeding nodes?
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, 20 May 2014 08:42:35 -0000

--089e0158ac7824a1a504f9d0dc16
Content-Type: text/plain; charset=UTF-8

Yeah I'm expecting port 8333 to go away in China at some point. Actually I
was expecting that years ago and was kind of surprised that the suppression
was being done via banks. Guess the GFW operators were just slow to catch
up.
On 20 May 2014 10:16, <bitcoingrant@gmx.com> wrote:

> Recently China has updated its firewall blocking bitcoin sites and pools.
> Whether this is simple blacklist or more sophisticated packet targeting
> is uncertain, however this update did spefically target VPN handshakes.
>
>  *Sent:* Monday, April 07, 2014 at 1:07 PM
> *From:* Drak <drak@zikula.org>
> *To:* "Mike Hearn" <mike@plan99.net>
> *Cc:* "Bitcoin Dev" <bitcoin-development@lists.sourceforge.net>
> *Subject:* Re: [Bitcoin-development] Why are we bleeding nodes?
>  For what it's worth, the number of nodes rose dramatically during the
> China bullrun (I recall 45k in China alone) and dropped as dramatically as
> the price after the first PBOC announcement designed to cool down bitcoin
> trading in China.
>
> On 7 April 2014 12:34, Mike Hearn <mike@plan99.net> wrote:
>>
>> At the start of February we had 10,000 bitcoin nodes. Now we have 8,500
>> and still falling:
>>
>>    http://getaddr.bitnodes.io/dashboard/chart/?days=60
>>
>> I know all the reasons why people *might* stop running a node (uses too
>> much disk space, bandwidth, lost interest etc). But does anyone have any
>> idea how we might get more insight into what's really going on? It'd be
>> convenient if the subVer contained the operating system, as then we could
>> tell if the bleed was mostly from desktops/laptops (Windows/Mac), which
>> would be expected, or from virtual servers (Linux), which would be more
>> concerning.
>>
>> When you set up a Tor node, you can add your email address to the config
>> file and the Tor project sends you emails from time to time about things
>> you should know about. If we did the same, we could have a little exit
>> survey: if your node disappears for long enough, we could email the
>> operator and ask why they stopped.
>>
>>
>> ------------------------------------------------------------------------------
>> Put Bad Developers to Shame
>> Dominate Development with Jenkins Continuous Integration
>> Continuously Automate Build, Test & Deployment
>> Start a new project now. Try Jenkins in the cloud.
>> http://p.sf.net/sfu/13600_Cloudbees_APR
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>
>  ------------------------------------------------------------------------------
> Put Bad Developers to Shame Dominate Development with Jenkins Continuous
> Integration Continuously Automate Build, Test & Deployment Start a new
> project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees_______________________________________________Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
>

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

<p dir=3D"ltr">Yeah I&#39;m expecting port 8333 to go away in China at some=
 point. Actually I was expecting that years ago and was kind of surprised t=
hat the suppression was being done via banks. Guess the GFW operators were =
just slow to catch up.</p>

<div class=3D"gmail_quote">On 20 May 2014 10:16,  &lt;<a href=3D"mailto:bit=
coingrant@gmx.com">bitcoingrant@gmx.com</a>&gt; wrote:<br type=3D"attributi=
on"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">
<div><div style=3D"font-family:Verdana;font-size:12.0px"><div>
<div><span style=3D"font-family:Verdana,sans-serif,Arial,&#39;Trebuchet MS&=
#39;;font-size:13px;line-height:1.6em">Recently China has updated its firew=
all blocking bitcoin sites and pools. Whether this is simple blacklist or m=
ore=C2=A0</span><span style=3D"font-family:Verdana,sans-serif,Arial,&#39;Tr=
ebuchet MS&#39;;font-size:13px;line-height:1.6em">sophisticated</span><span=
 style=3D"font-family:Verdana,sans-serif,Arial,&#39;Trebuchet MS&#39;;font-=
size:13px;line-height:1.6em">=C2=A0packet targeting is uncertain, however t=
his update did spefically target VPN handshakes.</span></div>


<div>=C2=A0</div>

<div>
<div name=3D"quote" style=3D"margin:10px 5px 5px 10px;padding:10px 0 10px 1=
0px;border-left:2px solid #c3d9e5;word-wrap:break-word">
<div style=3D"margin:0 0 10px 0"><b>Sent:</b>=C2=A0Monday, April 07, 2014 a=
t 1:07 PM<br>
<b>From:</b>=C2=A0Drak &lt;<a href=3D"mailto:drak@zikula.org" target=3D"_bl=
ank">drak@zikula.org</a>&gt;<br>
<b>To:</b>=C2=A0&quot;Mike Hearn&quot; &lt;<a href=3D"mailto:mike@plan99.ne=
t" target=3D"_blank">mike@plan99.net</a>&gt;<br>
<b>Cc:</b>=C2=A0&quot;Bitcoin Dev&quot; &lt;<a href=3D"mailto:bitcoin-devel=
opment@lists.sourceforge.net" target=3D"_blank">bitcoin-development@lists.s=
ourceforge.net</a>&gt;<br>
<b>Subject:</b>=C2=A0Re: [Bitcoin-development] Why are we bleeding nodes?</=
div>

<div name=3D"quoted-content">
<div>For what it&#39;s worth, the number of nodes rose dramatically during =
the China bullrun (I recall 45k in China alone) and dropped as dramatically=
 as the price after the first PBOC announcement designed to cool down bitco=
in trading in China.</div>


<div class=3D"gmail_extra">=C2=A0
<div class=3D"gmail_quote">On 7 April 2014 12:34, Mike Hearn <span>&lt;<a h=
ref=3D"http://mike@plan99.net" target=3D"_blank">mike@plan99.net</a>&gt;</s=
pan> wrote:

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 0.8ex;border-left:1=
.0px rgb(204,204,204) solid;padding-left:1.0ex">
<div>At the start of February we had 10,000 bitcoin nodes. Now we have 8,50=
0 and still falling:
<div>=C2=A0</div>

<div>=C2=A0 =C2=A0<a href=3D"http://getaddr.bitnodes.io/dashboard/chart/?da=
ys=3D60" target=3D"_blank">http://getaddr.bitnodes.io/dashboard/chart/?days=
=3D60</a></div>

<div>=C2=A0</div>

<div>I know all the reasons why people <i>might</i>=C2=A0stop running a nod=
e (uses too much disk space, bandwidth, lost interest etc). But does anyone=
 have any idea how we might get more insight into what&#39;s really going o=
n? It&#39;d be convenient if the subVer contained the operating system, as =
then we could tell if the bleed was mostly from desktops/laptops (Windows/M=
ac), which would be expected, or from virtual servers (Linux), which would =
be more concerning.</div>


<div>=C2=A0</div>

<div>When you set up a Tor node, you can add your email address to the conf=
ig file and the Tor project sends you emails from time to time about things=
 you should know about. If we did the same, we could have a little exit sur=
vey: if your node disappears for long enough, we could email the operator a=
nd ask why they stopped.</div>

</div>
<br>
---------------------------------------------------------------------------=
---<br>
Put Bad Developers to Shame<br>
Dominate Development with Jenkins Continuous Integration<br>
Continuously Automate Build, Test &amp; Deployment<br>
Start a new project now. Try Jenkins in the cloud.<br>
<a href=3D"http://p.sf.net/sfu/13600_Cloudbees_APR" target=3D"_blank">http:=
//p.sf.net/sfu/13600_Cloudbees_APR</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"http://Bitcoin-development@lists.sourceforge.net" target=3D"_bla=
nk">Bitcoin-development@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
=C2=A0</blockquote>
</div>
</div>
---------------------------------------------------------------------------=
--- Put Bad Developers to Shame Dominate Development with Jenkins Continuou=
s Integration Continuously Automate Build, Test &amp; Deployment Start a ne=
w project now. Try Jenkins in the cloud. <a href=3D"http://p.sf.net/sfu/136=
00_Cloudbees_______________________________________________" target=3D"_bla=
nk">http://p.sf.net/sfu/13600_Cloudbees____________________________________=
___________</a> Bitcoin-development mailing list <a href=3D"mailto:Bitcoin-=
development@lists.sourceforge.net" target=3D"_blank">Bitcoin-development@li=
sts.sourceforge.net</a> <a href=3D"https://lists.sourceforge.net/lists/list=
info/bitcoin-development" target=3D"_blank">https://lists.sourceforge.net/l=
ists/listinfo/bitcoin-development</a></div>

</div>
</div>
</div>

<div>=C2=A0</div>

<div>=C2=A0</div></div></div>
</blockquote></div>

--089e0158ac7824a1a504f9d0dc16--