<?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: Making CAPTCHA Usable</title>
	<atom:link href="http://www.designinginteractive.com/user-experience/making-captcha-usable/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.designinginteractive.com/user-experience/making-captcha-usable/</link>
	<description>Usable Web Applications with Web Standards</description>
	<lastBuildDate>Tue, 27 Jul 2010 20:50:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: beth</title>
		<link>http://www.designinginteractive.com/user-experience/making-captcha-usable/comment-page-1/#comment-169</link>
		<dc:creator>beth</dc:creator>
		<pubDate>Thu, 21 Feb 2008 19:26:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/2007/09/16/how-to-make-captcha-usable/#comment-169</guid>
		<description>&lt;p&gt;I&#039;ve always said fighting comment spam is the responsibility of the blogger/site owner, and not their commenters or users. Why make interacting with you or your site any more difficult than necessary?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;ve always said fighting comment spam is the responsibility of the blogger/site owner, and not their commenters or users. Why make interacting with you or your site any more difficult than necessary?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe F.</title>
		<link>http://www.designinginteractive.com/user-experience/making-captcha-usable/comment-page-1/#comment-168</link>
		<dc:creator>Joe F.</dc:creator>
		<pubDate>Thu, 21 Feb 2008 19:19:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/2007/09/16/how-to-make-captcha-usable/#comment-168</guid>
		<description>&lt;p&gt;Interesting approach.  Not sure how spambots are going to work around this one.  Especially if you use a long string for your ID.  But, going the simple registration route, if you ensure your site suppots OpenID, this would be no big deal.  Otherwise, I probably wouldn&#039;t comment, because who needs YET ANOTHER username &amp; password?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Interesting approach.  Not sure how spambots are going to work around this one.  Especially if you use a long string for your ID.  But, going the simple registration route, if you ensure your site suppots OpenID, this would be no big deal.  Otherwise, I probably wouldn&#8217;t comment, because who needs YET ANOTHER username &amp; password?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danny Sedor</title>
		<link>http://www.designinginteractive.com/user-experience/making-captcha-usable/comment-page-1/#comment-17</link>
		<dc:creator>Danny Sedor</dc:creator>
		<pubDate>Mon, 17 Sep 2007 03:55:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/2007/09/16/how-to-make-captcha-usable/#comment-17</guid>
		<description>&lt;p&gt;While I find the use of CAPTCHA&#039;s to be a pain and I have often had to try 2, maybe 3 times to get the correct code from the jumbled image, I also think that the hidden form field will have its own set of problems and be circumvented rather quickly by determined spammers. 
I would propose a simple registration for the website you wish to blog/comment on. Once registered you can set your browser to auto-populate the information on each subsequent visit. 
The layer of security is still there. The user only has to be slightly inconvenienced once (during the initial visit), and the developer/admin does not have to continue to monitor the hidden field to see if the obstacle has been overcome.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>While I find the use of CAPTCHA&#8217;s to be a pain and I have often had to try 2, maybe 3 times to get the correct code from the jumbled image, I also think that the hidden form field will have its own set of problems and be circumvented rather quickly by determined spammers.<br />
I would propose a simple registration for the website you wish to blog/comment on. Once registered you can set your browser to auto-populate the information on each subsequent visit.<br />
The layer of security is still there. The user only has to be slightly inconvenienced once (during the initial visit), and the developer/admin does not have to continue to monitor the hidden field to see if the obstacle has been overcome.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
