public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Jeremy Spilman <jeremy@taplink.co>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Area of Focus
Date: Sat, 20 Dec 2014 21:30:03 +0000	[thread overview]
Message-ID: <CAAS2fgRB33c+JGphkT72OiRnLY_41b5Ufkfmff=4u-yB1oq2Qw@mail.gmail.com> (raw)
In-Reply-To: <op.xq5yue2cyldrnw@laptop-air>

On Sat, Dec 20, 2014 at 11:14 AM, Jeremy Spilman <jeremy@taplink.co> wrote:
>> are dnsseeds being blocked
> ostensibly because they are acting as dyanamic DNS infrastructure for
> malware sites?

Pretty much appears to be the case. In every instance it appears to be
automated. This predates the msft no-ip.com stuff.
We also had similar problems with the IRC based method that the
software originally used.

It's the same story for mail relay spam blacklisting.  There is a
whole industry out there selling people semi-snake-oil blocking
solutions to make the baddness of the internet go away. The low margin
business demands a cheap and highly automated approach... lots of
inappropriate things get blocked. Nagging people to fix things is time
consuming, better to move out of their sights a bit, so that they at
least have to specifically target Bitcoin. If they do, it'll at least
be worth the time spent fixing it.

I believe opendns is blocking all of sipa.be still as we speak, so if
you'd like to see it for yourself try to load http://bitcoin.sipa.be
while using opendns.



  parent reply	other threads:[~2014-12-20 21:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-20  7:42 [Bitcoin-development] Area of Focus Will Bickford
2014-12-20  8:57 ` Matt Corallo
2014-12-20 10:08   ` Roy Badami
2014-12-20 11:14     ` Jeremy Spilman
2014-12-20 21:20       ` Matt Corallo
2014-12-20 21:30       ` Gregory Maxwell [this message]
2014-12-20 18:27   ` Christian Decker
2014-12-20 21:26 ` Jeff Garzik
2014-12-20 22:37   ` Will Bickford

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='CAAS2fgRB33c+JGphkT72OiRnLY_41b5Ufkfmff=4u-yB1oq2Qw@mail.gmail.com' \
    --to=gmaxwell@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=jeremy@taplink.co \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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