<?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: Rel=&#8221;nofollow&#8221; Follow Up</title>
	<atom:link href="http://www.lattimore.id.au/2005/02/05/relnofollow-follow-up/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lattimore.id.au/2005/02/05/relnofollow-follow-up/</link>
	<description>The day to day goings on of our family</description>
	<lastBuildDate>Mon, 30 Jan 2012 20:24:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Hanspeter</title>
		<link>http://www.lattimore.id.au/2005/02/05/relnofollow-follow-up/comment-page-1/#comment-4429</link>
		<dc:creator>Hanspeter</dc:creator>
		<pubDate>Sun, 30 Apr 2006 12:07:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.lattimore.id.au/2005/02/09/relnofollow-follow-up/#comment-4429</guid>
		<description>The only problem with downloading the linked site is that it can affect page views, particularly important with regards to ads on that page.  A page with ads will register page views and then money will be exchanged between the advertiser and host site.  So if I was a spammer, I would spam my site everywhere, then all those blogs will download my site to verify its non-spammyness, and my ad hits will skyrocket, making me money from the advertisers.

Softcoding the comment.cgi URL and using a sessionID as well in the URL is probably the best way mentioned.  It&#039;s a little more resource intensive because it then requires more database hits to compare who&#039;s using the URL, but it&#039;s a small prize.  Even more than sessionID, I would use an ID that&#039;s a derivative of the session AND the instance of hitting &quot;Leave a comment&quot; with some expiration time.

Plus it is safer because you&#039;re in 100% control of everthing in the process, avoiding any unintentional consequences from using 3rd party content (foreign page).

heh.  I just noticed this post is a year old :)</description>
		<content:encoded><![CDATA[<p>The only problem with downloading the linked site is that it can affect page views, particularly important with regards to ads on that page.  A page with ads will register page views and then money will be exchanged between the advertiser and host site.  So if I was a spammer, I would spam my site everywhere, then all those blogs will download my site to verify its non-spammyness, and my ad hits will skyrocket, making me money from the advertisers.</p>
<p>Softcoding the comment.cgi URL and using a sessionID as well in the URL is probably the best way mentioned.  It&#8217;s a little more resource intensive because it then requires more database hits to compare who&#8217;s using the URL, but it&#8217;s a small prize.  Even more than sessionID, I would use an ID that&#8217;s a derivative of the session AND the instance of hitting &#8220;Leave a comment&#8221; with some expiration time.</p>
<p>Plus it is safer because you&#8217;re in 100% control of everthing in the process, avoiding any unintentional consequences from using 3rd party content (foreign page).</p>
<p>heh.  I just noticed this post is a year old :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Al</title>
		<link>http://www.lattimore.id.au/2005/02/05/relnofollow-follow-up/comment-page-1/#comment-6</link>
		<dc:creator>Al</dc:creator>
		<pubDate>Tue, 15 Feb 2005 06:07:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.lattimore.id.au/2005/02/09/relnofollow-follow-up/#comment-6</guid>
		<description>That is a pretty similar stand point to what I take on the matter as well Scott. I honestly believe that if it wasn&#039;t either cost effective for spammers, that would initially kill off a significant volume of them. If the huge rewards for people to spam was removed as well, then clearly it would die off as there wouldn&#039;t be a &lt;em&gt;good reason&lt;/em&gt; for them to continue.

I suppose the reality of it is, as long as money can be made through the internet, then there will always be some reason for them to spam. Our job will be to continually make it harder and harder for them to do it efficiently.

I&#039;ve been pondering writing a couple of different plugins for WordPress to test some of these thoughts out. The one I&#039;m quite interested in, is pulling down the linked site and scanning it for keywords. Chances has it, that if it is a spammer the site will be related to porn, gambling or drugs of some sort. If you get x number of positive hits for it, you either don&#039;t display the post at all, don&#039;t link the URL or link the URL with rel=&quot;nofollow&quot; (I&#039;d prefer to not link it period to be honest).

Have you considered any new sorts of anti-spam type mechanisms at all?</description>
		<content:encoded><![CDATA[<p>That is a pretty similar stand point to what I take on the matter as well Scott. I honestly believe that if it wasn&#8217;t either cost effective for spammers, that would initially kill off a significant volume of them. If the huge rewards for people to spam was removed as well, then clearly it would die off as there wouldn&#8217;t be a <em>good reason</em> for them to continue.</p>
<p>I suppose the reality of it is, as long as money can be made through the internet, then there will always be some reason for them to spam. Our job will be to continually make it harder and harder for them to do it efficiently.</p>
<p>I&#8217;ve been pondering writing a couple of different plugins for WordPress to test some of these thoughts out. The one I&#8217;m quite interested in, is pulling down the linked site and scanning it for keywords. Chances has it, that if it is a spammer the site will be related to porn, gambling or drugs of some sort. If you get x number of positive hits for it, you either don&#8217;t display the post at all, don&#8217;t link the URL or link the URL with rel=&#8221;nofollow&#8221; (I&#8217;d prefer to not link it period to be honest).</p>
<p>Have you considered any new sorts of anti-spam type mechanisms at all?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Yang</title>
		<link>http://www.lattimore.id.au/2005/02/05/relnofollow-follow-up/comment-page-1/#comment-5</link>
		<dc:creator>Scott Yang</dc:creator>
		<pubDate>Mon, 14 Feb 2005 23:48:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.lattimore.id.au/2005/02/09/relnofollow-follow-up/#comment-5</guid>
		<description>I think fighting spam is all about maximising spammers&#039; effort thus minimising their profit. Hopefully by making spamming not cost effective, it&#039;ll gradually die down. For example, eliminating automation of spamming by require some kind of human intervention (enter in text in gif, confirmation email, random sanity-checking questions, etc). Slow down the rate of spamming (compulsory delay in the script, throttling, etc). Content filtering (spammy words filtering, RBL-style central database, etc).

Or alternatively, maybe we should just have a law that heavily penalise the spammers :)
</description>
		<content:encoded><![CDATA[<p>I think fighting spam is all about maximising spammers&#8217; effort thus minimising their profit. Hopefully by making spamming not cost effective, it&#8217;ll gradually die down. For example, eliminating automation of spamming by require some kind of human intervention (enter in text in gif, confirmation email, random sanity-checking questions, etc). Slow down the rate of spamming (compulsory delay in the script, throttling, etc). Content filtering (spammy words filtering, RBL-style central database, etc).</p>
<p>Or alternatively, maybe we should just have a law that heavily penalise the spammers :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

