<?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: Using Radio Buttons to Combat Form Spam</title>
	<atom:link href="http://www.waterfallweb.net/archives/2007/10/using-radio-buttons-to-combat-form-spam/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.waterfallweb.net/archives/2007/10/using-radio-buttons-to-combat-form-spam/</link>
	<description>website design, development, marketing and management (and the odd gadget)</description>
	<lastBuildDate>Thu, 20 May 2010 15:15:01 +1000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rob Davis</title>
		<link>http://www.waterfallweb.net/archives/2007/10/using-radio-buttons-to-combat-form-spam/comment-page-1/#comment-2928</link>
		<dc:creator>Rob Davis</dc:creator>
		<pubDate>Mon, 18 May 2009 04:00:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.waterfallweb.net/archives/2007/10/using-radio-buttons-to-combat-form-spam/#comment-2928</guid>
		<description>This is funny, I just ran into some problems with spam bots posting one of my client&#039;s forms, and thought of this same solution after researching other methods.

Have you had any success with this?

Regardless I&#039;m going to try it out as it seems the absolute simplest solution. The forms only get posted to me and my client (since that is all I allow server-side!), but they are still annoying.</description>
		<content:encoded><![CDATA[<p>This is funny, I just ran into some problems with spam bots posting one of my client&#8217;s forms, and thought of this same solution after researching other methods.</p>
<p>Have you had any success with this?</p>
<p>Regardless I&#8217;m going to try it out as it seems the absolute simplest solution. The forms only get posted to me and my client (since that is all I allow server-side!), but they are still annoying.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jylan Wynne</title>
		<link>http://www.waterfallweb.net/archives/2007/10/using-radio-buttons-to-combat-form-spam/comment-page-1/#comment-2704</link>
		<dc:creator>Jylan Wynne</dc:creator>
		<pubDate>Thu, 11 Oct 2007 02:44:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.waterfallweb.net/archives/2007/10/using-radio-buttons-to-combat-form-spam/#comment-2704</guid>
		<description>I suppose for the Google Toolbar problem you&#039;d just have to name it something that the Toolbar doesn&#039;t fill in automatically. An id (or class) of “email” or “name” would probably trigger the toolbar, as would any other class with these words contained in it.

The confirmation page is probably the safest way to go, but you would risk losing genuinue comments because people may close the window as soon as it reloads again or something else like that.</description>
		<content:encoded><![CDATA[<p>I suppose for the Google Toolbar problem you&#8217;d just have to name it something that the Toolbar doesn&#8217;t fill in automatically. An id (or class) of “email” or “name” would probably trigger the toolbar, as would any other class with these words contained in it.</p>
<p>The confirmation page is probably the safest way to go, but you would risk losing genuinue comments because people may close the window as soon as it reloads again or something else like that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://www.waterfallweb.net/archives/2007/10/using-radio-buttons-to-combat-form-spam/comment-page-1/#comment-2702</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Wed, 10 Oct 2007 11:25:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.waterfallweb.net/archives/2007/10/using-radio-buttons-to-combat-form-spam/#comment-2702</guid>
		<description>Actually, the more I think about it, the Google Toolbar Autofill could be a problem. (&lt;a href=&quot;http://haacked.com/archive/2007/09/11/honeypot-captcha.aspx#52088&quot; rel=&quot;nofollow&quot;&gt;Refer this comment&lt;/a&gt;)

If the honeypot field is automatically filled in by a 3rd party tool like that, how do you deal with that error? Explaining what happened to the average user would be hard enough, but what steps could we reasonably expect them to take to rectify it?

Something else I stumbled upon tonight is the &lt;a ref=&quot;http://www.sitepoint.com/forums/showpost.php?p=3563385&amp;postcount=7&quot; rel=&quot;nofollow&quot;&gt;use of a confirmation page&lt;/a&gt;.

That might work too...</description>
		<content:encoded><![CDATA[<p>Actually, the more I think about it, the Google Toolbar Autofill could be a problem. (<a href="http://haacked.com/archive/2007/09/11/honeypot-captcha.aspx#52088" rel="nofollow">Refer this comment</a>)</p>
<p>If the honeypot field is automatically filled in by a 3rd party tool like that, how do you deal with that error? Explaining what happened to the average user would be hard enough, but what steps could we reasonably expect them to take to rectify it?</p>
<p>Something else I stumbled upon tonight is the <a ref="http://www.sitepoint.com/forums/showpost.php?p=3563385&#038;postcount=7" rel="nofollow">use of a confirmation page</a>.</p>
<p>That might work too&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://www.waterfallweb.net/archives/2007/10/using-radio-buttons-to-combat-form-spam/comment-page-1/#comment-2700</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Wed, 10 Oct 2007 09:41:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.waterfallweb.net/archives/2007/10/using-radio-buttons-to-combat-form-spam/#comment-2700</guid>
		<description>Haven&#039;t heard of that one before - but that&#039;s a pretty good idea. As long as you&#039;re careful what you name it, it&#039;s an unobtrusive method. Good call.</description>
		<content:encoded><![CDATA[<p>Haven&#8217;t heard of that one before &#8211; but that&#8217;s a pretty good idea. As long as you&#8217;re careful what you name it, it&#8217;s an unobtrusive method. Good call.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jylan Wynne</title>
		<link>http://www.waterfallweb.net/archives/2007/10/using-radio-buttons-to-combat-form-spam/comment-page-1/#comment-2699</link>
		<dc:creator>Jylan Wynne</dc:creator>
		<pubDate>Wed, 10 Oct 2007 08:43:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.waterfallweb.net/archives/2007/10/using-radio-buttons-to-combat-form-spam/#comment-2699</guid>
		<description>I can&#039;t spot any obvious disadvantages with your example, but I was listening to the 94th boagworld podcast and they mentioned something called a &lt;a href=&quot;http://haacked.com/archive/2007/09/11/honeypot-captcha.aspx&quot; rel=&quot;nofollow&quot;&gt;honeypot captcha&lt;/a&gt;. This works by including a hidden field in your form and give it an id or class of &quot;body.&quot; The spam bots would then go crazy and fill it out.

It would then be easy to check if the comment was genuine or not by checking to see if that field had been filled in.</description>
		<content:encoded><![CDATA[<p>I can&#8217;t spot any obvious disadvantages with your example, but I was listening to the 94th boagworld podcast and they mentioned something called a <a href="http://haacked.com/archive/2007/09/11/honeypot-captcha.aspx" rel="nofollow">honeypot captcha</a>. This works by including a hidden field in your form and give it an id or class of &#8220;body.&#8221; The spam bots would then go crazy and fill it out.</p>
<p>It would then be easy to check if the comment was genuine or not by checking to see if that field had been filled in.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
