<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: No Comments for You</title>
	<atom:link href="http://www.metaphoriclabs.com/articles/no-comments-for-you/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.metaphoriclabs.com/articles/no-comments-for-you/</link>
	<description>Experiential Serendipity</description>
	<lastBuildDate>Thu, 02 Feb 2012 19:06:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: IO ERROR</title>
		<link>http://www.metaphoriclabs.com/articles/no-comments-for-you/comment-page-1/#comment-468</link>
		<dc:creator>IO ERROR</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.metaphoriclabs.com/2005/no-comments-for-you/#comment-468</guid>
		<description>&lt;p&gt;No offense intended. The block causing you to be unable to post was removed shortly afterward, since I determined it (1) had way too many false positives, and (2) the comment spam coming from Comcast was getting caught by other means anyway. It also killed your trackback, which is why I didn&#8217;t find out about this posting for a good month or so. Sorry!
&lt;/p&gt;
&lt;p&gt;
The 45% figure came from pulling &lt;a href=&quot;http://www.arin.net/&quot;&gt;ARIN&lt;/a&gt; records on every unique IP from which I received comment spam on 31 Dec and 1 Jan. Comcast has done quite a lot to stop email spam, but at least in parts of the network, but it hasn&#8217;t been enough to make a very big dent in the overall outgoing spam flow. For instance, you may find they block outgoing port 25, but do they also block port 587? I also notice they are blocking a lot of &lt;em&gt;incoming&lt;/em&gt; ports as well now, but not quite enough. There are way too many malicious programs out there, and 65535 ports to choose from...and at some point, these blocks will start interfering with legitimate connections. Or the already-installed spambot can just contact a remote site for instructions. I know of at least one spambot that does this, making the inbound blocks ineffective.
&lt;/p&gt;
&lt;p&gt;
As for captchas, I hate them with a passion, and you simply will never see one on my site. I decided moderation was probably the best route to go with such comments. Although there are still a few addresses which are blocked entirely, anyone affected can easily have their IP address removed from the block list.
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>No offense intended. The block causing you to be unable to post was removed shortly afterward, since I determined it (1) had way too many false positives, and (2) the comment spam coming from Comcast was getting caught by other means anyway. It also killed your trackback, which is why I didn&#8217;t find out about this posting for a good month or so. Sorry!
</p>
<p>
The 45% figure came from pulling <a href="http://www.arin.net/">ARIN</a> records on every unique IP from which I received comment spam on 31 Dec and 1 Jan. Comcast has done quite a lot to stop email spam, but at least in parts of the network, but it hasn&#8217;t been enough to make a very big dent in the overall outgoing spam flow. For instance, you may find they block outgoing port 25, but do they also block port 587? I also notice they are blocking a lot of <em>incoming</em> ports as well now, but not quite enough. There are way too many malicious programs out there, and 65535 ports to choose from&#8230;and at some point, these blocks will start interfering with legitimate connections. Or the already-installed spambot can just contact a remote site for instructions. I know of at least one spambot that does this, making the inbound blocks ineffective.
</p>
<p>
As for captchas, I hate them with a passion, and you simply will never see one on my site. I decided moderation was probably the best route to go with such comments. Although there are still a few addresses which are blocked entirely, anyone affected can easily have their IP address removed from the block list.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

