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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <shadders.del@gmail.com>) id 1R0vgY-0007i5-37
for bitcoin-development@lists.sourceforge.net;
Tue, 06 Sep 2011 13:27:30 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.216.43 as permitted sender)
client-ip=209.85.216.43; envelope-from=shadders.del@gmail.com;
helo=mail-qw0-f43.google.com;
Received: from mail-qw0-f43.google.com ([209.85.216.43])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1R0vgS-00046A-Qu
for bitcoin-development@lists.sourceforge.net;
Tue, 06 Sep 2011 13:27:30 +0000
Received: by qwm42 with SMTP id 42so4594408qwm.30
for <bitcoin-development@lists.sourceforge.net>;
Tue, 06 Sep 2011 06:27:19 -0700 (PDT)
Received: by 10.52.94.176 with SMTP id dd16mr4930448vdb.369.1315315639318;
Tue, 06 Sep 2011 06:27:19 -0700 (PDT)
Received: from [10.1.1.50] (155.88-67-202.dynamic.dsl.syd.iprimus.net.au
[202.67.88.155])
by mx.google.com with ESMTPS id be19sm91617vdb.21.2011.09.06.06.27.16
(version=SSLv3 cipher=OTHER); Tue, 06 Sep 2011 06:27:18 -0700 (PDT)
Message-ID: <4E661FAE.9020008@gmail.com>
Date: Tue, 06 Sep 2011 23:27:10 +1000
From: Steve <shadders.del@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
rv:1.9.2.21) Gecko/20110831 Thunderbird/3.1.13
MIME-Version: 1.0
To: Mike Hearn <mike@plan99.net>
References: <4E65CEE6.7030002@gmail.com> <4E65DA06.9060403@gmail.com> <CALxbBHUajARXc1oA-NjD+U8hW5uSqF=u4ZHHBfcmT_O8GjpNiA@mail.gmail.com>
<CANEZrP0VXDUs_mAKCVKD1Q0ijyb989oADrCN1zTZ1nnN_JQ=cQ@mail.gmail.com>
In-Reply-To: <CANEZrP0VXDUs_mAKCVKD1Q0ijyb989oADrCN1zTZ1nnN_JQ=cQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.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
(shadders.del[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-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
0.3 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1R0vgS-00046A-Qu
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Building a node crawler to map network
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: shadders.del@gmail.com
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, 06 Sep 2011 13:27:30 -0000
Hi Mike,
I've looked but can't find a post like you're talking about. Can you
point me to it?
If so then bollocks... I'm looking for something useful to do atm.
PoolServerJ is in a holding pattern atm as I've stabilisied all the bugs
I know about and am waiting for several pools to finish testing and move
into production so I'm twiddling thumbs trying to figure out how to
spend my time.
On 06/09/11 22:49, Mike Hearn wrote:
> Actually Steve, take a look at the bitcoinj mailing list today.
> Somebody has already built this and has it running. It's accumulating
> data at the moment, they'll announce it more widely soon. But I think
> there's no need to duplicate work.
|
