<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>nicholasjon.com :: a weblog &gt;&gt; posts tagged: spam</title>
    <link>http://www.nicholasjon.com/</link>
    <pubDate>Tue, 28 Nov 2006 20:00:40 GMT</pubDate>
    <description>nicholasjon.com :: an rss feed</description>
    <image>
      <url>http://www.nicholasjon.com/images/n_ficon.gif</url>
      <link>http://www.nicholasjon.com/</link>
      <title>nicholasjon.com :: favicon</title>
    </image>
    <item>
      <title>Comment spam</title>
      <link>http://www.nicholasjon.com/permalink/2006/11/28/comment_spam</link>
      <description>&lt;p&gt;Being on the receiving end of comment spam sucks.  I use two techniques to try to slow it down, but some still manages to get through.&lt;/p&gt;


	&lt;p&gt;The first of my techniques is wrapping the actual comment posting form in an ajax request.  This weeds out bots that can&amp;#8217;t handle javascript or XMLHttpRequests.  The second is a double-encoded hidden form field in the actual comment posting form.  Both the name and the value of that form change every few minutes, rendering old name-value pairs useless and basically preventing comment spam posting without actually hitting the site immediately beforehand.&lt;/p&gt;


	&lt;p&gt;Like I said, some manages to get through anyway.  But I&amp;#8217;m trying to do what I can without resorting to blacklists or capchas &amp;mdash; which I think are tantamount to giving up, though I admit they may be in my near-future.&lt;/p&gt;</description>
      <pubDate>Tue, 28 Nov 2006 20:00:40 GMT</pubDate>
      <guid>http://www.nicholasjon.com/permalink/2006/11/28/comment_spam</guid>
      <author>nicholasjon@nicholasjon.com (Nick)</author>
    </item>
  </channel>
</rss>
