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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1WX7p5-0006NQ-C3
for bitcoin-development@lists.sourceforge.net;
Mon, 07 Apr 2014 11:34:43 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.169 as permitted sender)
client-ip=209.85.214.169; envelope-from=mh.in.england@gmail.com;
helo=mail-ob0-f169.google.com;
Received: from mail-ob0-f169.google.com ([209.85.214.169])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WX7p4-0007M1-Cn
for bitcoin-development@lists.sourceforge.net;
Mon, 07 Apr 2014 11:34:43 +0000
Received: by mail-ob0-f169.google.com with SMTP id va2so6413943obc.14
for <bitcoin-development@lists.sourceforge.net>;
Mon, 07 Apr 2014 04:34:37 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.219.167 with SMTP id pp7mr84516obc.85.1396870477088;
Mon, 07 Apr 2014 04:34:37 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.96.180 with HTTP; Mon, 7 Apr 2014 04:34:37 -0700 (PDT)
Date: Mon, 7 Apr 2014 13:34:37 +0200
X-Google-Sender-Auth: R7EjnLvxbXnvC-SnfBci9_2HWtY
Message-ID: <CANEZrP2rgiQHpekEpFviJ22QsiV+s-F2pqosaZOA5WrRtJx5pg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=089e0141ab82958d3004f6724005
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: 1WX7p4-0007M1-Cn
Subject: [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: Mon, 07 Apr 2014 11:34:43 -0000
--089e0141ab82958d3004f6724005
Content-Type: text/plain; charset=UTF-8
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.
--089e0141ab82958d3004f6724005
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">At the start of February we had 10,000 bitcoin nodes. Now =
we have 8,500 and still falling:<div><br></div><div>=C2=A0 =C2=A0<a href=3D=
"http://getaddr.bitnodes.io/dashboard/chart/?days=3D60">http://getaddr.bitn=
odes.io/dashboard/chart/?days=3D60</a><br>
</div><div><br></div><div>I know all the reasons why people <i>might</i>=C2=
=A0stop 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 deskto=
ps/laptops (Windows/Mac), which would be expected, or from virtual servers =
(Linux), which would be more concerning.</div>
<div><br></div><div>When you set up a Tor node, you can add your email addr=
ess to the config file and the Tor project sends you emails from time to ti=
me 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.</div>
</div>
--089e0141ab82958d3004f6724005--
|
