summaryrefslogtreecommitdiff
path: root/84/d1978a87144a0e3529dab8ab6673b840ffa1d2
blob: 4e8abff6d9f8ea3ac20e081f20a2782ef5e2a36f (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
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1Qocc7-0006fc-Ce
	for bitcoin-development@lists.sourceforge.net;
	Wed, 03 Aug 2011 14:40:05 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.220.175 as permitted sender)
	client-ip=209.85.220.175; envelope-from=mh.in.england@gmail.com;
	helo=mail-vx0-f175.google.com; 
Received: from mail-vx0-f175.google.com ([209.85.220.175])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Qocc6-0007dT-P1
	for bitcoin-development@lists.sourceforge.net;
	Wed, 03 Aug 2011 14:40:03 +0000
Received: by vxj14 with SMTP id 14so152461vxj.34
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 03 Aug 2011 07:39:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.90.48 with SMTP id bt16mr3194551vdb.197.1312382397178; Wed,
	03 Aug 2011 07:39:57 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.52.158.233 with HTTP; Wed, 3 Aug 2011 07:39:57 -0700 (PDT)
In-Reply-To: <CAPiTikUc5At5r8XH_5paQ2odx_bib0FGO4OqhGCeQEZ_VRkz0w@mail.gmail.com>
References: <CANEZrP1-BaNmKhSPXSe2sjH0-DPm62_=OQ_S6aCT3-nLdFLLGA@mail.gmail.com>
	<CAJ1JLtuRhqwcCWjv+H2XUjsX-Za9ZkSkOsH3t=JaUu1581RGUA@mail.gmail.com>
	<CANEZrP2Cr1mVcj3CQQNx6BeWSb=hzxawva2Lz=sAbjx4AwYdmw@mail.gmail.com>
	<CAJ1JLttf+h5J8ehmx1j5P1GiGYAUiLN=fGjSV_dLoy72XQohfA@mail.gmail.com>
	<CAPiTikUc5At5r8XH_5paQ2odx_bib0FGO4OqhGCeQEZ_VRkz0w@mail.gmail.com>
Date: Wed, 3 Aug 2011 16:39:57 +0200
X-Google-Sender-Auth: iYKqNGaMQzRql3xJ1tkyzBCRS98
Message-ID: <CANEZrP0DDkeuDwNZA+WV3LGXp0Q31ZJeJAWiV=6Xm+f=ZusrhQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Douglas Huff <dhuff@jrbobdobbs.org>
Content-Type: multipart/alternative; boundary=bcaec50160cb97e38604a99ad68a
X-Spam-Score: 0.4 (/)
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
	0.9 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1Qocc6-0007dT-P1
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] DNS seeds returning gone peers
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, 03 Aug 2011 14:40:05 -0000

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

>
> There's a bigger problem here honestly. The p2p network is just starved for
> connectable slots.
>
Suggestions:

- massively increasing all the anti-DoS limits in 0.4, so far they've caused
a lot more damage than they solved.

- broadcasting an "upgrade now" type announcement. The alert system is
intended for informing users when there's a threat to system stability and
that's exactly what has been happening recently.

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

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><p>There&#39;s a=
 bigger problem here honestly. The p2p network is just starved for connecta=
ble slots.</p>
</blockquote><div>Suggestions:</div><div><br></div><div>- massively increas=
ing all the anti-DoS limits in 0.4, so far they&#39;ve caused a lot more da=
mage than they solved.<br><br></div><div>- broadcasting an &quot;upgrade no=
w&quot; type announcement. The alert system is intended for informing users=
 when there&#39;s a threat to system stability and that&#39;s exactly what =
has been happening recently.</div>
</div>

--bcaec50160cb97e38604a99ad68a--