Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] 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 1XCnjV-0005yu-9c for bitcoin-development@lists.sourceforge.net; Thu, 31 Jul 2014 10:37:13 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.53 as permitted sender) client-ip=209.85.219.53; envelope-from=mh.in.england@gmail.com; helo=mail-oa0-f53.google.com; Received: from mail-oa0-f53.google.com ([209.85.219.53]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XCnjU-0007cQ-B5 for bitcoin-development@lists.sourceforge.net; Thu, 31 Jul 2014 10:37:13 +0000 Received: by mail-oa0-f53.google.com with SMTP id j17so1808462oag.26 for <bitcoin-development@lists.sourceforge.net>; Thu, 31 Jul 2014 03:37:05 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.60.158.8 with SMTP id wq8mr15471693oeb.40.1406803025028; Thu, 31 Jul 2014 03:37:05 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.35.234 with HTTP; Thu, 31 Jul 2014 03:37:04 -0700 (PDT) In-Reply-To: <CAH+ZByEFqBmUvA_ZO_8MzaYvfUopHY1x=rGaMeq8fL4_2q1uJg@mail.gmail.com> References: <CAJHLa0O1EP8aUn4KLbo3OvzjgVfF8onrMjNnkRAnuWHwbofWBQ@mail.gmail.com> <CA+s+GJDUbm7Z9FeQr1otuEPXn0RRq+KL=kS3GJT3j3TeWz_n5Q@mail.gmail.com> <CAPg+sBhmkcW-7TYQ7TxAYvMsLrckcja+wPDow80a9Yoo1KdgMw@mail.gmail.com> <CAH+ZByEFqBmUvA_ZO_8MzaYvfUopHY1x=rGaMeq8fL4_2q1uJg@mail.gmail.com> Date: Thu, 31 Jul 2014 12:37:04 +0200 X-Google-Sender-Auth: _ohfLw4b5Gpsa-H49JkcBVM7O64 Message-ID: <CANEZrP2HHPUnsymDnRLd=-Ox-RD8RezM7TvpYeAw_np4JM4Bdw@mail.gmail.com> From: Mike Hearn <mike@plan99.net> To: Neil Fincham <neil@asdf.co.nz> Content-Type: multipart/alternative; boundary=047d7bd6ac48936d4804ff7adaed 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: 1XCnjU-0007cQ-B5 Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> Subject: Re: [Bitcoin-development] Abusive and broken bitcoin seeders 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: Thu, 31 Jul 2014 10:37:13 -0000 --047d7bd6ac48936d4804ff7adaed Content-Type: text/plain; charset=UTF-8 > > I suspect it is something that is going to have to be dealt with in the > future (I just don't know how yet). > The web has managed to survive despite constant fast crawls being the norm for the past 10 years or so. I wouldn't worry too much about this unless you can prove that a big chunk of your nodes resources are going to answering ver queries. --047d7bd6ac48936d4804ff7adaed Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo= ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c= cc solid;padding-left:1ex"><div dir=3D"ltr"><div>I suspect it is something = that is going to have to be dealt with in the future (I just don't know= how yet).=C2=A0</div> </div></blockquote><div><br></div><div>The web has managed to survive despi= te constant fast crawls being the norm for the past 10 years or so. I would= n't worry too much about this unless you can prove that a big chunk of = your nodes resources are going to answering ver queries.=C2=A0</div> </div></div></div> --047d7bd6ac48936d4804ff7adaed--