<?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: Magic word comment spamtrap</title>
	<atom:link href="http://www.logophile.org/blog/2005/06/28/magic-word-comment-spamtrap/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.logophile.org/blog/2005/06/28/magic-word-comment-spamtrap/</link>
	<description>blog of a logophile (not "logos", but "λόγος")</description>
	<lastBuildDate>Mon, 06 Feb 2012 10:21:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: tikitu</title>
		<link>http://www.logophile.org/blog/2005/06/28/magic-word-comment-spamtrap/comment-page-1/#comment-1239</link>
		<dc:creator>tikitu</dc:creator>
		<pubDate>Wed, 13 Jul 2005 15:06:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.logophile.org/blog/?p=60#comment-1239</guid>
		<description>&lt;p&gt;Ah, good points. Especially like the hidden field,  given that point about spiders not actually reading pages at all. But surely the easiest thing of all would be a find-replace in the comment-handling script that just adds a prefix to the fields expected. The installation process for standard blogging tools should do this. (Of course the next-gen spiders then &lt;em&gt;will&lt;/em&gt; read the pages to find out the prefix...)&lt;/p&gt;

&lt;p&gt;Wrt blacklisting: that&#039;s more-or-less what Spam Karma does, only it builds its own blacklist. You get downgraded if you make lots and lots of comments real fast, or if you include too many links (this keeps tripping Erik up :-).&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Ah, good points. Especially like the hidden field,  given that point about spiders not actually reading pages at all. But surely the easiest thing of all would be a find-replace in the comment-handling script that just adds a prefix to the fields expected. The installation process for standard blogging tools should do this. (Of course the next-gen spiders then <em>will</em> read the pages to find out the prefix&#8230;)</p>

<p>Wrt blacklisting: that&#8217;s more-or-less what Spam Karma does, only it builds its own blacklist. You get downgraded if you make lots and lots of comments real fast, or if you include too many links (this keeps tripping Erik up :-).</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Robin</title>
		<link>http://www.logophile.org/blog/2005/06/28/magic-word-comment-spamtrap/comment-page-1/#comment-1238</link>
		<dc:creator>Robin</dc:creator>
		<pubDate>Wed, 13 Jul 2005 12:43:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.logophile.org/blog/?p=60#comment-1238</guid>
		<description>&lt;p&gt;Some of your ideas won&#039;t work, in particular the &#039;clear this field&#039; ones. As I understand it (having written robots that do form submission, although not evil spammy ones), they don&#039;t simulate a page being submitted by going to it, finding all the form details, constructing a suitable response, and submitting that. Instead they simply post straight to the comment handling script (note: they may have gotten more advanced due to people trying to avoid them)&lt;/p&gt;

&lt;p&gt;What I&#039;d suggest:
* Rename the comment handling script, so the bots can&#039;t find it.
* Put a hidden field in the page that is required by the comment script (similar to the &#039;type this phrase&#039; thing, except the submitter doesn&#039;t have to do any work, as a real browser will take care of it.) For bonus marks, have the field value be
a) random for a specific page, or
b) random for a time duration (sucky if people take a long long time to type the comment, but there are ways to deal with that)
* Have the comment script do a blacklist lookup on any URLs. There are blacklists that track URLs that are being spamvertised, if the same thing has been sent out in mass mails, it may well be there.&lt;/p&gt;

&lt;p&gt;Any of these can be worked around by evil spammers, but that&#039;s not the point. In rp parlance: &quot;I don&#039;t have to run faster than the troll, I just have to run faster than you!&quot;. Make yourself harder to spam than the average joe, and you&#039;ll find they go for the lower hanging fruit. (Make what you will of the implication that you&#039;re a fruit :)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Some of your ideas won&#8217;t work, in particular the &#8216;clear this field&#8217; ones. As I understand it (having written robots that do form submission, although not evil spammy ones), they don&#8217;t simulate a page being submitted by going to it, finding all the form details, constructing a suitable response, and submitting that. Instead they simply post straight to the comment handling script (note: they may have gotten more advanced due to people trying to avoid them)</p>

<p>What I&#8217;d suggest:
* Rename the comment handling script, so the bots can&#8217;t find it.
* Put a hidden field in the page that is required by the comment script (similar to the &#8216;type this phrase&#8217; thing, except the submitter doesn&#8217;t have to do any work, as a real browser will take care of it.) For bonus marks, have the field value be
a) random for a specific page, or
b) random for a time duration (sucky if people take a long long time to type the comment, but there are ways to deal with that)
* Have the comment script do a blacklist lookup on any URLs. There are blacklists that track URLs that are being spamvertised, if the same thing has been sent out in mass mails, it may well be there.</p>

<p>Any of these can be worked around by evil spammers, but that&#8217;s not the point. In rp parlance: &#8220;I don&#8217;t have to run faster than the troll, I just have to run faster than you!&#8221;. Make yourself harder to spam than the average joe, and you&#8217;ll find they go for the lower hanging fruit. (Make what you will of the implication that you&#8217;re a fruit :)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: tikitu</title>
		<link>http://www.logophile.org/blog/2005/06/28/magic-word-comment-spamtrap/comment-page-1/#comment-1237</link>
		<dc:creator>tikitu</dc:creator>
		<pubDate>Wed, 29 Jun 2005 12:09:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.logophile.org/blog/?p=60#comment-1237</guid>
		<description>&lt;p&gt;That is indeed true. I just happen to dislike them (&lt;em&gt;my&lt;/em&gt; character recognition often isn&#039;t good enough, either). (I could bleat about blind people, screen readers, etc, but I somehow doubt that anyone blind is reading my blog...)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>That is indeed true. I just happen to dislike them (<em>my</em> character recognition often isn&#8217;t good enough, either). (I could bleat about blind people, screen readers, etc, but I somehow doubt that anyone blind is reading my blog&#8230;)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: erik</title>
		<link>http://www.logophile.org/blog/2005/06/28/magic-word-comment-spamtrap/comment-page-1/#comment-1236</link>
		<dc:creator>erik</dc:creator>
		<pubDate>Wed, 29 Jun 2005 12:00:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.logophile.org/blog/?p=60#comment-1236</guid>
		<description>&lt;p&gt;why not just a rendered image with a password?  Character recognition won&#039;t be good enough in the upcoming years to recognise misformed letters ... Since i installed it i didn&#039;t have any comments, euh, spam anymore ...
e.g. &lt;a href=&quot;http://uberdork.supertwist.net/2005/03/13/plug-it-in-plug-it-in/&quot; rel=&quot;nofollow&quot;&gt;http://uberdork.supertwist.net/2005/03/13/plug-it-in-plug-it-in/&lt;/a&gt;
See my comment forms for an example&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>why not just a rendered image with a password?  Character recognition won&#8217;t be good enough in the upcoming years to recognise misformed letters &#8230; Since i installed it i didn&#8217;t have any comments, euh, spam anymore &#8230;
e.g. <a href="http://uberdork.supertwist.net/2005/03/13/plug-it-in-plug-it-in/" rel="nofollow">http://uberdork.supertwist.net/2005/03/13/plug-it-in-plug-it-in/</a>
See my comment forms for an example</p>]]></content:encoded>
	</item>
</channel>
</rss>

