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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pieter.wuille@gmail.com>) id 1WkYxY-00058d-3P
for bitcoin-development@lists.sourceforge.net;
Wed, 14 May 2014 13:11:00 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.223.176 as permitted sender)
client-ip=209.85.223.176; envelope-from=pieter.wuille@gmail.com;
helo=mail-ie0-f176.google.com;
Received: from mail-ie0-f176.google.com ([209.85.223.176])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WkYxW-0001Ip-T8
for bitcoin-development@lists.sourceforge.net;
Wed, 14 May 2014 13:11:00 +0000
Received: by mail-ie0-f176.google.com with SMTP id ar20so1818872iec.21
for <bitcoin-development@lists.sourceforge.net>;
Wed, 14 May 2014 06:10:53 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.42.120.15 with SMTP id d15mr3212840icr.35.1400073052956;
Wed, 14 May 2014 06:10:52 -0700 (PDT)
Received: by 10.50.127.201 with HTTP; Wed, 14 May 2014 06:10:52 -0700 (PDT)
Received: by 10.50.127.201 with HTTP; Wed, 14 May 2014 06:10:52 -0700 (PDT)
In-Reply-To: <537355C8.2090700@gmail.com>
References: <536FAFEA.5050404@gmail.com>
<CA+s+GJAoLTrujeHVEUZYDR1mNUFHVsLhH9BYPntrxLKzMm_AEw@mail.gmail.com>
<AE9CCC5A-0DAB-4F5A-93D6-C2CA9484C4A4@krellan.net>
<537355C8.2090700@gmail.com>
Date: Wed, 14 May 2014 15:10:52 +0200
Message-ID: <CAPg+sBhCouFoYxwEjq09C+wXrgojdzsedBM+tJJpNCwp0JsQFQ@mail.gmail.com>
From: Pieter Wuille <pieter.wuille@gmail.com>
To: Jameson Lopp <jameson.lopp@gmail.com>
Content-Type: multipart/alternative; boundary=90e6ba613c3afb2e2804f95be869
X-Spam-Score: -0.3 (/)
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
(pieter.wuille[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.3 URIBL_RHS_DOB Contains an URI of a new domain (Day Old Bread)
[URIs: statoshi.info]
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: 1WkYxW-0001Ip-T8
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] statoshi.info is now live
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: Wed, 14 May 2014 13:11:00 -0000
--90e6ba613c3afb2e2804f95be869
Content-Type: text/plain; charset=ISO-8859-1
On May 14, 2014 1:42 PM, "Jameson Lopp" <jameson.lopp@gmail.com> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Thanks; I've received several suggestions for other metrics to collect
that I hope to implement soon, but you're right in that tracking per-peer
pings is a different type of metric than what I'm currently collecting. I
actually noted the lack of pong messages in a post I made a few weeks ago:
http://coinchomp.com/2014/04/27/peeking-hood-running-bitcoin-node/
See pull request #2784.
(Sent from my phone)
--
Pieter
--90e6ba613c3afb2e2804f95be869
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<p dir=3D"ltr"><br>
On May 14, 2014 1:42 PM, "Jameson Lopp" <<a href=3D"mailto:jam=
eson.lopp@gmail.com">jameson.lopp@gmail.com</a>> wrote:<br>
><br>
> -----BEGIN PGP SIGNED MESSAGE-----<br>
> Hash: SHA1<br>
><br>
> Thanks; I've received several suggestions for other metrics to col=
lect that I hope to implement soon, but you're right in that tracking p=
er-peer pings is a different type of metric than what I'm currently col=
lecting. I actually noted the lack of pong messages in a post I made a few =
weeks ago: <a href=3D"http://coinchomp.com/2014/04/27/peeking-hood-running-=
bitcoin-node/">http://coinchomp.com/2014/04/27/peeking-hood-running-bitcoin=
-node/</a></p>
<p dir=3D"ltr">See pull request #2784.</p>
<p dir=3D"ltr">(Sent from my phone)</p>
<p dir=3D"ltr">-- <br>
Pieter</p>
--90e6ba613c3afb2e2804f95be869--
|
