<?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: Blog Usability: Avoid Spam Comments</title>
	<atom:link href="http://justaddwater.dk/2006/06/24/blog-usability-avoid-spam-comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://justaddwater.dk/2006/06/24/blog-usability-avoid-spam-comments/</link>
	<description>Instant Usability &#38; Web Standards</description>
	<lastBuildDate>Sat, 28 Jan 2012 13:44:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Redstar aka John</title>
		<link>http://justaddwater.dk/2006/06/24/blog-usability-avoid-spam-comments/comment-page-1/#comment-452646</link>
		<dc:creator>Redstar aka John</dc:creator>
		<pubDate>Sat, 18 Oct 2008 19:14:17 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2006/06/24/blog-usability-avoid-spam-comments/#comment-452646</guid>
		<description>I came here because I was looking for some info about comment spam. I dont have a problem with the spam bots, but some guy started to implant commentspam by hand.

Intresting solution you used here at that time..</description>
		<content:encoded><![CDATA[<p>I came here because I was looking for some info about comment spam. I dont have a problem with the spam bots, but some guy started to implant commentspam by hand.</p>
<p>Intresting solution you used here at that time..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christy</title>
		<link>http://justaddwater.dk/2006/06/24/blog-usability-avoid-spam-comments/comment-page-1/#comment-279512</link>
		<dc:creator>Christy</dc:creator>
		<pubDate>Wed, 03 Oct 2007 09:54:42 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2006/06/24/blog-usability-avoid-spam-comments/#comment-279512</guid>
		<description>Spam Filtering may reduce the number of spam for a short while but you cant say that it is an ultimate solution to Spamming. The reason is that the Spammers are aware of these filtering techniques whether it is Filtering with CAPTCHA or some other. There are many websites available that are providing the information on Anti-Spamming Solutions but most of this information is either irrelevant or not useful. I have recently visited a website 
http://www.anti-spam-info.com
and i found it much reliable for the anti spamming.</description>
		<content:encoded><![CDATA[<p>Spam Filtering may reduce the number of spam for a short while but you cant say that it is an ultimate solution to Spamming. The reason is that the Spammers are aware of these filtering techniques whether it is Filtering with CAPTCHA or some other. There are many websites available that are providing the information on Anti-Spamming Solutions but most of this information is either irrelevant or not useful. I have recently visited a website<br />
<a href="http://www.anti-spam-info.com">http://www.anti-spam-info.com</a><br />
and i found it much reliable for the anti spamming.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: justaddwater.dk &#124; Spam Blog Posted 182 Articles in One Day</title>
		<link>http://justaddwater.dk/2006/06/24/blog-usability-avoid-spam-comments/comment-page-1/#comment-119317</link>
		<dc:creator>justaddwater.dk &#124; Spam Blog Posted 182 Articles in One Day</dc:creator>
		<pubDate>Mon, 02 Apr 2007 00:34:54 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2006/06/24/blog-usability-avoid-spam-comments/#comment-119317</guid>
		<description>[...] we have written about our spam comment countermeasures in &#8220;how to avoid spam comments&#8221; (part 1, part 2), and the last 2 months since we passed 100,000 spam comments, we have had another 57,000 [...]</description>
		<content:encoded><![CDATA[<p>[...] we have written about our spam comment countermeasures in &#8220;how to avoid spam comments&#8221; (part 1, part 2), and the last 2 months since we passed 100,000 spam comments, we have had another 57,000 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: justaddwater.dk &#124; 100,000 Blog Spam Comments</title>
		<link>http://justaddwater.dk/2006/06/24/blog-usability-avoid-spam-comments/comment-page-1/#comment-78338</link>
		<dc:creator>justaddwater.dk &#124; 100,000 Blog Spam Comments</dc:creator>
		<pubDate>Tue, 06 Feb 2007 11:45:26 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2006/06/24/blog-usability-avoid-spam-comments/#comment-78338</guid>
		<description>[...] We have for example been blocking certain keywords that we found where common in spam that slipped through Akismet, or we have been changing the standard WordPress URL for posting comments. Finally we have incorporated a little htaccess hack that validates the posters referral URL. This should of cause be our own domain justaddwater.dk, but many spammers actually put some garbage into this header field - and we can then easily block it directly in the Apache web server before it even reaches WordPress. [...]</description>
		<content:encoded><![CDATA[<p>[...] We have for example been blocking certain keywords that we found where common in spam that slipped through Akismet, or we have been changing the standard WordPress URL for posting comments. Finally we have incorporated a little htaccess hack that validates the posters referral URL. This should of cause be our own domain justaddwater.dk, but many spammers actually put some garbage into this header field &#8211; and we can then easily block it directly in the Apache web server before it even reaches WordPress. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elena</title>
		<link>http://justaddwater.dk/2006/06/24/blog-usability-avoid-spam-comments/comment-page-1/#comment-21527</link>
		<dc:creator>Elena</dc:creator>
		<pubDate>Sat, 28 Oct 2006 15:51:15 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2006/06/24/blog-usability-avoid-spam-comments/#comment-21527</guid>
		<description>Most popular CAPTCHA types alredy recognize by spammers. I hate spammers. Every day i get a 50-120 letters to e-mail and over 100 comments into blog. It&#039;s crazy! Spam filters is not best way...</description>
		<content:encoded><![CDATA[<p>Most popular CAPTCHA types alredy recognize by spammers. I hate spammers. Every day i get a 50-120 letters to e-mail and over 100 comments into blog. It&#8217;s crazy! Spam filters is not best way&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: justaddwater.dk &#124; CAPTCHA usability: Humane alternative to CAPTCHA</title>
		<link>http://justaddwater.dk/2006/06/24/blog-usability-avoid-spam-comments/comment-page-1/#comment-20242</link>
		<dc:creator>justaddwater.dk &#124; CAPTCHA usability: Humane alternative to CAPTCHA</dc:creator>
		<pubDate>Mon, 23 Oct 2006 13:30:31 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2006/06/24/blog-usability-avoid-spam-comments/#comment-20242</guid>
		<description>[...] Blog usability: Avoid spam comments [...]</description>
		<content:encoded><![CDATA[<p>[...] Blog usability: Avoid spam comments [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesper Rønn-Jensen</title>
		<link>http://justaddwater.dk/2006/06/24/blog-usability-avoid-spam-comments/comment-page-1/#comment-20177</link>
		<dc:creator>Jesper Rønn-Jensen</dc:creator>
		<pubDate>Mon, 23 Oct 2006 08:23:58 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2006/06/24/blog-usability-avoid-spam-comments/#comment-20177</guid>
		<description>HashCash plugin for wordpress may also be able to help:

&lt;a href=&quot;http://www.elliottback.com/wp/archives/2005/10/23/wordpress-hashcash-30-beta/&quot; rel=&quot;nofollow&quot;&gt;HashCash wordpress plugin&lt;/a&gt; by Elliott Back

&lt;blockquote cite=&quot;http://www.elliottback.com/wp/archives/2005/10/23/wordpress-hashcash-30-beta/&quot;&gt;
Every four hours, your blog picks a random large number (close to 32 bits). Whenever a visitor visits your permalink pages, an ajax call is made which retrieves some javascript. This javascript first decrypts itself, then executes itself again to retrieve the secret value, which it sets in the form. If a comment does not have this value, it is rejected. If a comment is rejected more than four times, the user is blocked for a specified period of time.
&lt;/blockquote&gt;</description>
		<content:encoded><![CDATA[<p>HashCash plugin for wordpress may also be able to help:</p>
<p><a href="http://www.elliottback.com/wp/archives/2005/10/23/wordpress-hashcash-30-beta/" rel="nofollow">HashCash wordpress plugin</a> by Elliott Back</p>
<blockquote cite="http://www.elliottback.com/wp/archives/2005/10/23/wordpress-hashcash-30-beta/"><p>
Every four hours, your blog picks a random large number (close to 32 bits). Whenever a visitor visits your permalink pages, an ajax call is made which retrieves some javascript. This javascript first decrypts itself, then executes itself again to retrieve the secret value, which it sets in the form. If a comment does not have this value, it is rejected. If a comment is rejected more than four times, the user is blocked for a specified period of time.
</p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesper Rønn-Jensen</title>
		<link>http://justaddwater.dk/2006/06/24/blog-usability-avoid-spam-comments/comment-page-1/#comment-7654</link>
		<dc:creator>Jesper Rønn-Jensen</dc:creator>
		<pubDate>Sat, 01 Jul 2006 21:36:06 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2006/06/24/blog-usability-avoid-spam-comments/#comment-7654</guid>
		<description>Emil, 
I agree with you that JavaScript encoding is a big accessibility problem. The
reason why it&#039;s listed under &quot;what we might do&quot; is because we might do it if we can&#039;t stop spam comments in other ways.

But for now, spam comments seem to have stopped, as we introduced a new trick Thomas wrote about recently: &quot;&lt;a href=&quot;http://justaddwater.dk/2006/06/28/blog-usability-avoid-spam-comments-part-2/&quot; rel=&quot;nofollow&quot;&gt;Avoid Spam Comments part 2&lt;/a&gt;&quot;.

One more thing, I think that &lt;strong&gt;the JavaScript trick could be done in a way that makes comments accessible and unobtrusive&lt;/strong&gt;:

Imagine that the form-tag action contains the &quot;usual&quot; URL: wp-post-comment.php (URL must not be illegal). Then, via JavaScript we rewrite URL to some other URL. This URL can receive comments with no further ado.

BUT if on the other hand, JavaScript is turned off, the original URL is posted to. I would then suggest a &lt;noscript&gt; element with a hidden field. The field should behave as a non-image CAPTCHA with a label like: &quot;add two and three and write result here:&quot;

The comment-receiving script on the original URL is then programmed so that comments are rejected without the text-based CAPTCHA (or held for moderation).

The method with the hidden field has similarities with &lt;a href=&quot;http://www.intertwingly.net/blog/2006/05/30/Captcha-this&quot; rel=&quot;nofollow&quot;&gt;Sam Ruby&#039;s original example&lt;/a&gt;, where he uses JavaScript to fill out a hidden field.

You should decide for yourself which methods are necessary in your blog. For us, (so far), CAPTCHA and JavaScript has not been necessary.</description>
		<content:encoded><![CDATA[<p>Emil,<br />
I agree with you that JavaScript encoding is a big accessibility problem. The<br />
reason why it&#8217;s listed under &#8220;what we might do&#8221; is because we might do it if we can&#8217;t stop spam comments in other ways.</p>
<p>But for now, spam comments seem to have stopped, as we introduced a new trick Thomas wrote about recently: &#8220;<a href="http://justaddwater.dk/2006/06/28/blog-usability-avoid-spam-comments-part-2/" rel="nofollow">Avoid Spam Comments part 2</a>&#8220;.</p>
<p>One more thing, I think that <strong>the JavaScript trick could be done in a way that makes comments accessible and unobtrusive</strong>:</p>
<p>Imagine that the form-tag action contains the &#8220;usual&#8221; URL: wp-post-comment.php (URL must not be illegal). Then, via JavaScript we rewrite URL to some other URL. This URL can receive comments with no further ado.</p>
<p>BUT if on the other hand, JavaScript is turned off, the original URL is posted to. I would then suggest a &lt;noscript&gt; element with a hidden field. The field should behave as a non-image CAPTCHA with a label like: &#8220;add two and three and write result here:&#8221;</p>
<p>The comment-receiving script on the original URL is then programmed so that comments are rejected without the text-based CAPTCHA (or held for moderation).</p>
<p>The method with the hidden field has similarities with <a href="http://www.intertwingly.net/blog/2006/05/30/Captcha-this" rel="nofollow">Sam Ruby&#8217;s original example</a>, where he uses JavaScript to fill out a hidden field.</p>
<p>You should decide for yourself which methods are necessary in your blog. For us, (so far), CAPTCHA and JavaScript has not been necessary.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emil Virkki</title>
		<link>http://justaddwater.dk/2006/06/24/blog-usability-avoid-spam-comments/comment-page-1/#comment-7609</link>
		<dc:creator>Emil Virkki</dc:creator>
		<pubDate>Fri, 30 Jun 2006 09:56:02 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2006/06/24/blog-usability-avoid-spam-comments/#comment-7609</guid>
		<description>Isn&#039;t encoding forms with JS a usability problem for users of mobile browsers and people who have disabled JavaScript?</description>
		<content:encoded><![CDATA[<p>Isn&#8217;t encoding forms with JS a usability problem for users of mobile browsers and people who have disabled JavaScript?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: justaddwater.dk &#124; Blog usability: Avoid spam comments (part 2)</title>
		<link>http://justaddwater.dk/2006/06/24/blog-usability-avoid-spam-comments/comment-page-1/#comment-7388</link>
		<dc:creator>justaddwater.dk &#124; Blog usability: Avoid spam comments (part 2)</dc:creator>
		<pubDate>Wed, 28 Jun 2006 17:26:28 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2006/06/24/blog-usability-avoid-spam-comments/#comment-7388</guid>
		<description>[...] In our previous article Blog usability: Avoid spam comments we discussed the two ways we currently where fighting spam comments on our blog: [...]</description>
		<content:encoded><![CDATA[<p>[...] In our previous article Blog usability: Avoid spam comments we discussed the two ways we currently where fighting spam comments on our blog: [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

