<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: WordPress Comment Spam</title>
	<link>http://www.sweeting.org/mark/blog/2004/11/23/wordpress-comment-spam</link>
	<description>The world according to marky moo</description>
	<pubDate>Sun, 12 Oct 2008 07:26:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.1</generator>

	<item>
		<title>By: Mark</title>
		<link>http://www.sweeting.org/mark/blog/2004/11/23/wordpress-comment-spam#comment-205</link>
		<author>Mark</author>
		<pubDate>Thu, 25 Nov 2004 19:53:44 +0000</pubDate>
		<guid>http://www.sweeting.org/mark/blog/2004/11/23/wordpress-comment-spam#comment-205</guid>
		<description>If only I had time to wite my own comments system. Nah, what's the point re-inventing the wheel where there are perfectly good systems out there already?

The only reasons I can see for someone to write their own blogging software are:

1) if they want to simply as a challenge (and they have the time) - still not a good argument,

2) they want to learn a language like PHP and need a project to learn it with.

3) They really have specialist needs (and you don't Ox!)</description>
		<content:encoded><![CDATA[<p>If only I had time to wite my own comments system. Nah, what&#8217;s the point re-inventing the wheel where there are perfectly good systems out there already?</p>
<p>The only reasons I can see for someone to write their own blogging software are:</p>
<p>1) if they want to simply as a challenge (and they have the time) - still not a good argument,</p>
<p>2) they want to learn a language like PHP and need a project to learn it with.</p>
<p>3) They really have specialist needs (and you don&#8217;t Ox!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ox</title>
		<link>http://www.sweeting.org/mark/blog/2004/11/23/wordpress-comment-spam#comment-202</link>
		<author>Ox</author>
		<pubDate>Thu, 25 Nov 2004 17:59:25 +0000</pubDate>
		<guid>http://www.sweeting.org/mark/blog/2004/11/23/wordpress-comment-spam#comment-202</guid>
		<description>teeheehee.... the beauties of having your own comments system *grin* *winks and runningtings*</description>
		<content:encoded><![CDATA[<p>teeheehee&#8230;. the beauties of having your own comments system *grin* *winks and runningtings*</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://www.sweeting.org/mark/blog/2004/11/23/wordpress-comment-spam#comment-200</link>
		<author>Rob</author>
		<pubDate>Wed, 24 Nov 2004 22:24:25 +0000</pubDate>
		<guid>http://www.sweeting.org/mark/blog/2004/11/23/wordpress-comment-spam#comment-200</guid>
		<description>My spider trap isn't really about simple IP-banning.  Well, it is sort-of, but not as a permanent, long-term solution.  The mechanics of it are founded on two elements of the architecture: a) any spammer is forced to brute-force crawl the site, and are funnelled into the trap right quick, and b) the IP ban effectively kills that session - immediately and without any interaction on my part.  It's an amazingly effective trap-door solution.

I clean out the .htaccess file on a regular basis, and even quicker if I see in the alerter email that the source address was that of a large ISP's proxy.  That being said, 99% of my hits aren't from ISP proxies.  The bottom line is that the mechanism is very effective and totally unobtrusive to the end user - it doesn't require entering cryptic strings, validating comments, or maintaining user accounts or whitelists.  I'm running it on four sites, and they're all blissfully comment-spam free.

Thanks for the link.</description>
		<content:encoded><![CDATA[<p>My spider trap isn&#8217;t really about simple IP-banning.  Well, it is sort-of, but not as a permanent, long-term solution.  The mechanics of it are founded on two elements of the architecture: a) any spammer is forced to brute-force crawl the site, and are funnelled into the trap right quick, and b) the IP ban effectively kills that session - immediately and without any interaction on my part.  It&#8217;s an amazingly effective trap-door solution.</p>
<p>I clean out the .htaccess file on a regular basis, and even quicker if I see in the alerter email that the source address was that of a large ISP&#8217;s proxy.  That being said, 99% of my hits aren&#8217;t from ISP proxies.  The bottom line is that the mechanism is very effective and totally unobtrusive to the end user - it doesn&#8217;t require entering cryptic strings, validating comments, or maintaining user accounts or whitelists.  I&#8217;m running it on four sites, and they&#8217;re all blissfully comment-spam free.</p>
<p>Thanks for the link.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://www.sweeting.org/mark/blog/2004/11/23/wordpress-comment-spam#comment-198</link>
		<author>Mark</author>
		<pubDate>Tue, 23 Nov 2004 14:27:22 +0000</pubDate>
		<guid>http://www.sweeting.org/mark/blog/2004/11/23/wordpress-comment-spam#comment-198</guid>
		<description>That's fine if you've got the time!</description>
		<content:encoded><![CDATA[<p>That&#8217;s fine if you&#8217;ve got the time!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: runningtings</title>
		<link>http://www.sweeting.org/mark/blog/2004/11/23/wordpress-comment-spam#comment-197</link>
		<author>runningtings</author>
		<pubDate>Tue, 23 Nov 2004 13:46:13 +0000</pubDate>
		<guid>http://www.sweeting.org/mark/blog/2004/11/23/wordpress-comment-spam#comment-197</guid>
		<description>build your own CMS, works for me...</description>
		<content:encoded><![CDATA[<p>build your own CMS, works for me&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://www.sweeting.org/mark/blog/2004/11/23/wordpress-comment-spam#comment-196</link>
		<author>Mark</author>
		<pubDate>Tue, 23 Nov 2004 10:50:30 +0000</pubDate>
		<guid>http://www.sweeting.org/mark/blog/2004/11/23/wordpress-comment-spam#comment-196</guid>
		<description>They're still at it! I've added Gudfly's &lt;a href="http://www.gudlyf.com/index.php?p=376"&gt;WP AuthImage&lt;/a&gt; hack/plugin. Lets see if that helps...</description>
		<content:encoded><![CDATA[<p>They&#8217;re still at it! I&#8217;ve added Gudfly&#8217;s <a href="http://www.gudlyf.com/index.php?p=376">WP AuthImage</a> hack/plugin. Lets see if that helps&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
