<?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: Honeypot filter as a Rack middleware</title>
	<atom:link href="http://mad.ly/2009/05/01/honeypot-filter-as-a-rack-middleware/feed/" rel="self" type="application/rss+xml" />
	<link>http://mad.ly/2009/05/01/honeypot-filter-as-a-rack-middleware/</link>
	<description>rails, jquery, flash, etc</description>
	<lastBuildDate>Sun, 20 Dec 2009 21:02:36 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: David</title>
		<link>http://mad.ly/2009/05/01/honeypot-filter-as-a-rack-middleware/comment-page-1/#comment-4780</link>
		<dc:creator>David</dc:creator>
		<pubDate>Sun, 20 Dec 2009 21:02:36 +0000</pubDate>
		<guid isPermaLink="false">http://mad.ly/?p=43#comment-4780</guid>
		<description>Would it make sense to block the ip address once the spammer tried to post to the honeypot field?  or would that be too harsh?</description>
		<content:encoded><![CDATA[<p>Would it make sense to block the ip address once the spammer tried to post to the honeypot field?  or would that be too harsh?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anko Painting</title>
		<link>http://mad.ly/2009/05/01/honeypot-filter-as-a-rack-middleware/comment-page-1/#comment-4001</link>
		<dc:creator>Anko Painting</dc:creator>
		<pubDate>Mon, 04 May 2009 22:31:03 +0000</pubDate>
		<guid isPermaLink="false">http://mad.ly/?p=43#comment-4001</guid>
		<description>Could the line;
&lt;div class=&quot;something_unique_to_your_app&quot;&gt;

be changed to
&lt;div class=&quot;&lt;%= HONEYPOT_FIELD_NAME %&gt;&quot;&gt;

to make it more DRY?

(third time&#039;s a charm)</description>
		<content:encoded><![CDATA[<p>Could the line;<br />
&lt;div class=&#8221;something_unique_to_your_app&#8221;&gt;</p>
<p>be changed to<br />
&lt;div class=&#8221;&lt;%= HONEYPOT_FIELD_NAME %&gt;&#8221;&gt;</p>
<p>to make it more DRY?</p>
<p>(third time&#8217;s a charm)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: almost effortless &#187; Weekly Digest, 5-3-09</title>
		<link>http://mad.ly/2009/05/01/honeypot-filter-as-a-rack-middleware/comment-page-1/#comment-3998</link>
		<dc:creator>almost effortless &#187; Weekly Digest, 5-3-09</dc:creator>
		<pubDate>Sun, 03 May 2009 23:36:03 +0000</pubDate>
		<guid isPermaLink="false">http://mad.ly/?p=43#comment-3998</guid>
		<description>[...] Honeypot filter as a Rack middleware Our site’s suggestion box got hammered by a spambot recently, so I created this simple Rack middleware to protect our app from any requests that include a honeypot field. [...]</description>
		<content:encoded><![CDATA[<p>[...] Honeypot filter as a Rack middleware Our site’s suggestion box got hammered by a spambot recently, so I created this simple Rack middleware to protect our app from any requests that include a honeypot field. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
