<?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: Avoiding CAPTCHA</title>
	<atom:link href="http://danielkitta.org/blog/2006/10/09/avoiding-captcha/feed/" rel="self" type="application/rss+xml" />
	<link>http://danielkitta.org/blog/2006/10/09/avoiding-captcha/</link>
	<description>Delusional ramblings of a narcistic individual.</description>
	<lastBuildDate>Fri, 11 Feb 2011 08:00:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: danielk</title>
		<link>http://danielkitta.org/blog/2006/10/09/avoiding-captcha/comment-page-1/#comment-34</link>
		<dc:creator>danielk</dc:creator>
		<pubDate>Thu, 23 Nov 2006 14:47:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.danielkitta.org/blog/2006/10/09/avoiding-captcha/#comment-34</guid>
		<description>Yes, I think that&#039;s also the version I actually installed. But that doesn&#039;t remove the requirement of ECMAScript to be supported and enabled, does it? Personally I don&#039;t have any qualms with JavaScript as such and have it enabled most of the time. However, making JavaScript a strict requirement for commenting on my blog is a measure I&#039;d rather avoid.

Basically, my policy for this site is that I don&#039;t care much how it looks in older browsers (say, anything released more than four years ago), as long as the content is still intelligible and the essential functionality is available. Posting comments should be possible without JavaScript, unless support for it some day becomes ubiquitous even among text browsers and on mobile devices. Although by that time spam bots will probably interpret it too.</description>
		<content:encoded><![CDATA[<p>Yes, I think that&#8217;s also the version I actually installed. But that doesn&#8217;t remove the requirement of ECMAScript to be supported and enabled, does it? Personally I don&#8217;t have any qualms with JavaScript as such and have it enabled most of the time. However, making JavaScript a strict requirement for commenting on my blog is a measure I&#8217;d rather avoid.</p>
<p>Basically, my policy for this site is that I don&#8217;t care much how it looks in older browsers (say, anything released more than four years ago), as long as the content is still intelligible and the essential functionality is available. Posting comments should be possible without JavaScript, unless support for it some day becomes ubiquitous even among text browsers and on mobile devices. Although by that time spam bots will probably interpret it too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elliott C. Back</title>
		<link>http://danielkitta.org/blog/2006/10/09/avoiding-captcha/comment-page-1/#comment-32</link>
		<dc:creator>Elliott C. Back</dc:creator>
		<pubDate>Thu, 23 Nov 2006 02:01:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.danielkitta.org/blog/2006/10/09/avoiding-captcha/#comment-32</guid>
		<description>You might want to, uh, check out a more recent version of Hashcash, just FYI.  I think it&#039;s at 3.2 right now ;)</description>
		<content:encoded><![CDATA[<p>You might want to, uh, check out a more recent version of Hashcash, just FYI.  I think it&#8217;s at 3.2 right now <img src='http://danielkitta.org/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Murray Cumming</title>
		<link>http://danielkitta.org/blog/2006/10/09/avoiding-captcha/comment-page-1/#comment-11</link>
		<dc:creator>Murray Cumming</dc:creator>
		<pubDate>Wed, 11 Oct 2006 17:46:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.danielkitta.org/blog/2006/10/09/avoiding-captcha/#comment-11</guid>
		<description>&gt; Akismet did flag it as spam but I still had to delete it all myself.

Yes, that&#039;s out of the question for me. Spam shouldn&#039;t require my time. The captcha stops spam (and disabled people, unfortunately) before it gets that far.</description>
		<content:encoded><![CDATA[<p>&gt; Akismet did flag it as spam but I still had to delete it all myself.</p>
<p>Yes, that&#8217;s out of the question for me. Spam shouldn&#8217;t require my time. The captcha stops spam (and disabled people, unfortunately) before it gets that far.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Moritz Angermann</title>
		<link>http://danielkitta.org/blog/2006/10/09/avoiding-captcha/comment-page-1/#comment-10</link>
		<dc:creator>Moritz Angermann</dc:creator>
		<pubDate>Wed, 11 Oct 2006 11:48:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.danielkitta.org/blog/2006/10/09/avoiding-captcha/#comment-10</guid>
		<description>Spam is a serious issue. Even for low profile pages. My site has only 10 to 15 views/day. Yet again I&#039;m getting sometimes hammered with spam.

Yesterday a whole netblock from the Ukraine was pushing comments and trackbacks at a 30 second&#039;s rate. Literally I got more spam then I was able to delete. Akismet did flag it as spam but I still had to delete it all myself. That is on Typo so I don&#039;t know how WP handles spam.

The most effective method I found is to have a jabber notifier that tells you about events on your blog and in case of an emergency just disable sidewide comments and trackbacks temporarily.

Another finding is that usually _one_ article will get spamed and the rest will be left uneffected. Those articles are, at least to my experience those with date quite a bit back in time.

&gt; First-time posts are always moderated so no spam should get through.

This might turn into a serious headache for spam unless it get&#039;s deleted automatically.

regards,
 Moritz Angermann</description>
		<content:encoded><![CDATA[<p>Spam is a serious issue. Even for low profile pages. My site has only 10 to 15 views/day. Yet again I&#8217;m getting sometimes hammered with spam.</p>
<p>Yesterday a whole netblock from the Ukraine was pushing comments and trackbacks at a 30 second&#8217;s rate. Literally I got more spam then I was able to delete. Akismet did flag it as spam but I still had to delete it all myself. That is on Typo so I don&#8217;t know how WP handles spam.</p>
<p>The most effective method I found is to have a jabber notifier that tells you about events on your blog and in case of an emergency just disable sidewide comments and trackbacks temporarily.</p>
<p>Another finding is that usually _one_ article will get spamed and the rest will be left uneffected. Those articles are, at least to my experience those with date quite a bit back in time.</p>
<p>&gt; First-time posts are always moderated so no spam should get through.</p>
<p>This might turn into a serious headache for spam unless it get&#8217;s deleted automatically.</p>
<p>regards,<br />
 Moritz Angermann</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Benni</title>
		<link>http://danielkitta.org/blog/2006/10/09/avoiding-captcha/comment-page-1/#comment-9</link>
		<dc:creator>Benni</dc:creator>
		<pubDate>Wed, 11 Oct 2006 11:34:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.danielkitta.org/blog/2006/10/09/avoiding-captcha/#comment-9</guid>
		<description>Akismet really kills off most spam comments. Sometimes I get 100/day so it&#039;s a nice to have Wordpress plugin. I&#039;d say it misses one in each thousand spam comments so it doesn&#039;t take much work to keep your blog free of spam.</description>
		<content:encoded><![CDATA[<p>Akismet really kills off most spam comments. Sometimes I get 100/day so it&#8217;s a nice to have WordPress plugin. I&#8217;d say it misses one in each thousand spam comments so it doesn&#8217;t take much work to keep your blog free of spam.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

