Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.223.175 as permitted sender)
	client-ip=209.85.223.175; envelope-from=gmaxwell@gmail.com;
	helo=mail-ie0-f175.google.com; 
MIME-Version: 1.0
In-Reply-To: <op.xq5yue2cyldrnw@laptop-air>
References: <CAB2qGxXDtxWxyLUCEZ9XQ4nP0U-Cj5Xiz9ac=vot1H+wzRCHrA@mail.gmail.com>
	<54953A11.1060202@bluematt.me>
	<20141220100816.GD7902@giles.gnomon.org.uk>
	<op.xq5yue2cyldrnw@laptop-air>
Date: Sat, 20 Dec 2014 21:30:03 +0000
Message-ID: <CAAS2fgRB33c+JGphkT72OiRnLY_41b5Ufkfmff=4u-yB1oq2Qw@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Jeremy Spilman <jeremy@taplink.co>
Content-Type: text/plain; charset=UTF-8
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Area of Focus
Precedence: list

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.