From: Mike Hearn <mike@plan99•net>
To: Neil Fincham <neil@asdf•co.nz>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Abusive and broken bitcoin seeders
Date: Thu, 31 Jul 2014 12:37:04 +0200 [thread overview]
Message-ID: <CANEZrP2HHPUnsymDnRLd=-Ox-RD8RezM7TvpYeAw_np4JM4Bdw@mail.gmail.com> (raw)
In-Reply-To: <CAH+ZByEFqBmUvA_ZO_8MzaYvfUopHY1x=rGaMeq8fL4_2q1uJg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 356 bytes --]
>
> 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.
[-- Attachment #2: Type: text/html, Size: 619 bytes --]
next prev parent reply other threads:[~2014-07-31 10:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 13:22 Jeff Garzik
2014-07-30 13:50 ` Wladimir
2014-07-30 13:57 ` Pieter Wuille
2014-07-30 21:03 ` Neil Fincham
2014-07-31 10:37 ` Mike Hearn [this message]
2014-07-31 12:59 ` Jameson Lopp
2014-07-30 22:53 ` Addy Yeow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANEZrP2HHPUnsymDnRLd=-Ox-RD8RezM7TvpYeAw_np4JM4Bdw@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=neil@asdf$(echo .)co.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox