<?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: War against the automated content scrapers</title>
	<atom:link href="http://venetsian.com/war-against-the-automated-content-scrapers/feed/" rel="self" type="application/rss+xml" />
	<link>http://venetsian.com/war-against-the-automated-content-scrapers/</link>
	<description>SEO Expert, Web Enterpreneur, Online Publishing Specialist</description>
	<lastBuildDate>Wed, 03 Mar 2010 17:36:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Venetsian</title>
		<link>http://venetsian.com/war-against-the-automated-content-scrapers/comment-page-1/#comment-338</link>
		<dc:creator>Venetsian</dc:creator>
		<pubDate>Wed, 13 May 2009 02:54:37 +0000</pubDate>
		<guid isPermaLink="false">http://venetsian.com/?p=84#comment-338</guid>
		<description>Yes I agree to a certain level, but it still blocks a large amount of spam bots. You can always add more user agents to the allowed list which solves your problem.
I think the best way is to have a centralized spam bot detection system but I don&#039;t think anybody will go for it since you will have to establish trust with this type of organization in order to use such service which makes it quite complicated to arrange. If somebody does make it then it will solve the spam bot issue once and for all. If you do know which IPs are attacking you then you should edit your .HTACCESS file to deny their ip address ranges. If you don&#039;t then .. well you are not protected.</description>
		<content:encoded><![CDATA[<p>Yes I agree to a certain level, but it still blocks a large amount of spam bots. You can always add more user agents to the allowed list which solves your problem.<br />
I think the best way is to have a centralized spam bot detection system but I don&#8217;t think anybody will go for it since you will have to establish trust with this type of organization in order to use such service which makes it quite complicated to arrange. If somebody does make it then it will solve the spam bot issue once and for all. If you do know which IPs are attacking you then you should edit your .HTACCESS file to deny their ip address ranges. If you don&#8217;t then .. well you are not protected.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: San Luis Obispo Events</title>
		<link>http://venetsian.com/war-against-the-automated-content-scrapers/comment-page-1/#comment-334</link>
		<dc:creator>San Luis Obispo Events</dc:creator>
		<pubDate>Wed, 13 May 2009 02:15:14 +0000</pubDate>
		<guid isPermaLink="false">http://venetsian.com/?p=84#comment-334</guid>
		<description>This is not a good solution to block bots. It is common for spam bots to use the User Agent of a real browser to get past this filter. Also, although some of the mobile phone browsers use Opera or Safari, this script would block all that don&#039;t use a standard browser.</description>
		<content:encoded><![CDATA[<p>This is not a good solution to block bots. It is common for spam bots to use the User Agent of a real browser to get past this filter. Also, although some of the mobile phone browsers use Opera or Safari, this script would block all that don&#8217;t use a standard browser.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anonymus</title>
		<link>http://venetsian.com/war-against-the-automated-content-scrapers/comment-page-1/#comment-299</link>
		<dc:creator>anonymus</dc:creator>
		<pubDate>Sun, 03 May 2009 19:25:44 +0000</pubDate>
		<guid isPermaLink="false">http://venetsian.com/?p=84#comment-299</guid>
		<description>Please note that lynx and other text-browsers will be banned
too by your php script</description>
		<content:encoded><![CDATA[<p>Please note that lynx and other text-browsers will be banned<br />
too by your php script</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Venetsian</title>
		<link>http://venetsian.com/war-against-the-automated-content-scrapers/comment-page-1/#comment-196</link>
		<dc:creator>Venetsian</dc:creator>
		<pubDate>Fri, 10 Apr 2009 19:08:34 +0000</pubDate>
		<guid isPermaLink="false">http://venetsian.com/?p=84#comment-196</guid>
		<description>&lt;a href=&quot;#comment-163&quot; rel=&quot;nofollow&quot;&gt;@okinawa&lt;/a&gt; 
Yes, you put that on top of the header so that it reads the user agent and returns the proper http header response code. If you print something before this code it won&#039;t work!! (should give you warning or error that header was already sent!).
Venetsian</description>
		<content:encoded><![CDATA[<p><a href="#comment-163" rel="nofollow">@okinawa</a><br />
Yes, you put that on top of the header so that it reads the user agent and returns the proper http header response code. If you print something before this code it won&#8217;t work!! (should give you warning or error that header was already sent!).<br />
Venetsian</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: okinawa</title>
		<link>http://venetsian.com/war-against-the-automated-content-scrapers/comment-page-1/#comment-163</link>
		<dc:creator>okinawa</dc:creator>
		<pubDate>Sat, 04 Apr 2009 11:25:49 +0000</pubDate>
		<guid isPermaLink="false">http://venetsian.com/?p=84#comment-163</guid>
		<description>I would love to read more about your thoughts on Google&#039;s duplicate content filter. I don&#039;t know much about it. Do you place this  in your website header?</description>
		<content:encoded><![CDATA[<p>I would love to read more about your thoughts on Google&#8217;s duplicate content filter. I don&#8217;t know much about it. Do you place this  in your website header?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
