<?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: Stealing content for profit.</title>
	<atom:link href="http://blog.ftwr.co.uk/archives/2006/05/26/stealing-content-for-profit/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ftwr.co.uk/archives/2006/05/26/stealing-content-for-profit/</link>
	<description>Random commentary...</description>
	<pubDate>Thu, 20 Nov 2008 08:34:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7-beta3-9771</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Peter Westwood &#187; antileech</title>
		<link>http://blog.ftwr.co.uk/archives/2006/05/26/stealing-content-for-profit/comment-page-1/#comment-16910</link>
		<dc:creator>Peter Westwood &#187; antileech</dc:creator>
		<pubDate>Thu, 12 Oct 2006 09:39:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ftwr.co.uk/archives/2006/05/26/stealing-content-for-profit/#comment-16910</guid>
		<description>[...] After the recent episodes of content theft that have been reported by myself and others Owen has written a new plugin called antileech which aims to make it easy to protect your sites against leechers. I have installed antileech on this site so please let me know if you are having any problems with my feeds.        Comment on this post [...]</description>
		<content:encoded><![CDATA[<p>[...] After the recent episodes of content theft that have been reported by myself and others Owen has written a new plugin called antileech which aims to make it easy to protect your sites against leechers. I have installed antileech on this site so please let me know if you are having any problems with my feeds.        Comment on this post [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Westwood &#187; The content thieves return</title>
		<link>http://blog.ftwr.co.uk/archives/2006/05/26/stealing-content-for-profit/comment-page-1/#comment-13914</link>
		<dc:creator>Peter Westwood &#187; The content thieves return</dc:creator>
		<pubDate>Sun, 13 Aug 2006 21:21:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ftwr.co.uk/archives/2006/05/26/stealing-content-for-profit/#comment-13914</guid>
		<description>[...] It seems that content theft is the current craze amongst wanabee adsense millionaires. So much so that they don&#8217;t even pay attention to the content they are stealing. The latest culprit &#8220;WordPress Planet&#8221; @ weblog-pla.net/wp is even stealing the content of my last post about content theft! Compare the original and the stolen copy As ever I have reported the culprit to google and expect there adsense account to die fairly soon.        Comment on this post [...]</description>
		<content:encoded><![CDATA[<p>[...] It seems that content theft is the current craze amongst wanabee adsense millionaires. So much so that they don&#8217;t even pay attention to the content they are stealing. The latest culprit &#8220;WordPress Planet&#8221; @ weblog-pla.net/wp is even stealing the content of my last post about content theft! Compare the original and the stolen copy As ever I have reported the culprit to google and expect there adsense account to die fairly soon.        Comment on this post [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: westi</title>
		<link>http://blog.ftwr.co.uk/archives/2006/05/26/stealing-content-for-profit/comment-page-1/#comment-7355</link>
		<dc:creator>westi</dc:creator>
		<pubDate>Fri, 26 May 2006 21:42:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ftwr.co.uk/archives/2006/05/26/stealing-content-for-profit/#comment-7355</guid>
		<description>I think the more people that contact google about the site the better.  Especially if your content is being taken too.
When I find sites like this I tend to contact google via the feedback links on the adsense ads themselves to ensure they get as much relavent information as possible.</description>
		<content:encoded><![CDATA[<p>I think the more people that contact google about the site the better.  Especially if your content is being taken too.<br />
When I find sites like this I tend to contact google via the feedback links on the adsense ads themselves to ensure they get as much relavent information as possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: miklb</title>
		<link>http://blog.ftwr.co.uk/archives/2006/05/26/stealing-content-for-profit/comment-page-1/#comment-7338</link>
		<dc:creator>miklb</dc:creator>
		<pubDate>Fri, 26 May 2006 20:08:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ftwr.co.uk/archives/2006/05/26/stealing-content-for-profit/#comment-7338</guid>
		<description>I've had issues with the site as well.  I hand pick items from RSS feeds, and write the posts, with links directly to the theme/plugin/tip authors, nothing aggregated about my site (I read hundreds of posts titles looking for content). Then to only to see my posts show up on that site burns me to no end.  Never thought about contacting google ads about it.  I too use a CC license through the feedburner options.
Would it help if more than one site contacted google?</description>
		<content:encoded><![CDATA[<p>I&#8217;ve had issues with the site as well.  I hand pick items from RSS feeds, and write the posts, with links directly to the theme/plugin/tip authors, nothing aggregated about my site (I read hundreds of posts titles looking for content). Then to only to see my posts show up on that site burns me to no end.  Never thought about contacting google ads about it.  I too use a CC license through the feedburner options.<br />
Would it help if more than one site contacted google?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
