<?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: Content theft on the rise: What now Scoble?</title>
	<atom:link href="http://www.blogherald.com/2005/06/01/content-theft-on-the-rise-what-now-scoble/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blogherald.com/2005/06/01/content-theft-on-the-rise-what-now-scoble/</link>
	<description>The leading source of news covering social media and the blogosphere.</description>
	<lastBuildDate>Mon, 13 Feb 2012 08:28:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: What Do You Do When Someone Steals Your Content &#171; Lorelle on WordPress</title>
		<link>http://www.blogherald.com/2005/06/01/content-theft-on-the-rise-what-now-scoble/comment-page-1/#comment-127505</link>
		<dc:creator>What Do You Do When Someone Steals Your Content &#171; Lorelle on WordPress</dc:creator>
		<pubDate>Sun, 08 Oct 2006 15:23:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2005/06/01/content-theft-on-the-rise-what-now-scoble/#comment-127505</guid>
		<description>[...] Content theft on the rise: What now Scoble? [...]</description>
		<content:encoded><![CDATA[<p>[...] Content theft on the rise: What now Scoble? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MagiCentric &#187; Reblog Follow-up</title>
		<link>http://www.blogherald.com/2005/06/01/content-theft-on-the-rise-what-now-scoble/comment-page-1/#comment-95147</link>
		<dc:creator>MagiCentric &#187; Reblog Follow-up</dc:creator>
		<pubDate>Sun, 28 May 2006 00:37:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2005/06/01/content-theft-on-the-rise-what-now-scoble/#comment-95147</guid>
		<description>[...] n original thought, a point-of-view that is your own. John LeBlanc sent me a link to an interesting reblog article and this is one of the mo [...]</description>
		<content:encoded><![CDATA[<p>[...] n original thought, a point-of-view that is your own. John LeBlanc sent me a link to an interesting reblog article and this is one of the mo [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lorelle on WordPress &#187; Content Theft from Feeds - It&#8217;s Time To Take Action</title>
		<link>http://www.blogherald.com/2005/06/01/content-theft-on-the-rise-what-now-scoble/comment-page-1/#comment-90474</link>
		<dc:creator>Lorelle on WordPress &#187; Content Theft from Feeds - It&#8217;s Time To Take Action</dc:creator>
		<pubDate>Fri, 21 Apr 2006 05:13:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2005/06/01/content-theft-on-the-rise-what-now-scoble/#comment-90474</guid>
		<description>[...]  Trend in Content Theft, which includes feed thieves.  There is a reference in the post of problems in the past  [...]</description>
		<content:encoded><![CDATA[<p>[...]  Trend in Content Theft, which includes feed thieves.  There is a reference in the post of problems in the past  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Lewis</title>
		<link>http://www.blogherald.com/2005/06/01/content-theft-on-the-rise-what-now-scoble/comment-page-1/#comment-30085</link>
		<dc:creator>Rob Lewis</dc:creator>
		<pubDate>Wed, 01 Jun 2005 16:17:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2005/06/01/content-theft-on-the-rise-what-now-scoble/#comment-30085</guid>
		<description>The disclaimer idea that Paul put forward above seems like a reasonable idea, but I doubt it would act as much of a deterrent, and whether people would report the stealing sites is another matter - is there another way of determining whether your RSS content has been stolen, e.g. with an image &quot;beacon&quot; which links back to your own website? Not sure whether that would work or even possible within XML, but the likelyhood is the theives would find a way of stripping that out anyway.

It&#039;s also probably the case that a lot of these sites are probably using this stolen dynamic content to feed search engines, getting visitors to come and maybe clicking on the AdSense ads they&#039;ve no doubt got on their pages. Excerpts seem like the way to go for the moment.</description>
		<content:encoded><![CDATA[<p>The disclaimer idea that Paul put forward above seems like a reasonable idea, but I doubt it would act as much of a deterrent, and whether people would report the stealing sites is another matter &#8211; is there another way of determining whether your RSS content has been stolen, e.g. with an image &#8220;beacon&#8221; which links back to your own website? Not sure whether that would work or even possible within XML, but the likelyhood is the theives would find a way of stripping that out anyway.</p>
<p>It&#8217;s also probably the case that a lot of these sites are probably using this stolen dynamic content to feed search engines, getting visitors to come and maybe clicking on the AdSense ads they&#8217;ve no doubt got on their pages. Excerpts seem like the way to go for the moment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John LeBlanc</title>
		<link>http://www.blogherald.com/2005/06/01/content-theft-on-the-rise-what-now-scoble/comment-page-1/#comment-29805</link>
		<dc:creator>John LeBlanc</dc:creator>
		<pubDate>Wed, 01 Jun 2005 12:44:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2005/06/01/content-theft-on-the-rise-what-now-scoble/#comment-29805</guid>
		<description>I&#039;m not sure how much more of a niche area in which one can participate than the world of performing magicians and mindreaders. So you can imagine my surprise and irritation to find a guy reblogging the feed from Escamoteurettes. (Even though my copyright notice is fairly plain in language.)

It took three days, several phone calls, and a number of emails before I found the owner of the site (thanks, whoever you are, who came up with the brilliant idea of proxy registrations) and convinced him I was dead serious about him ceasing from republishing my stuff.

The Reader&#039;s Digest version of the story is I was called a luddite for not embracing reblogging. &quot;Why would I not want my content republished?&quot; Uh, maybe because I&#039;d rather visitors to my web site to read my content there? Maybe I have something of a problem with someone republishing my work -- insignificant as it is, it&#039;s still my work -- and not even bother to credit me or provide a link back to my web site, let alone ask my permission?

Yes, I know it&#039;s a bit like two ants fighting for a crumb of bread. But to the ant, it&#039;s a pretty big thing.

I applaud those who publish under the Creative Commons license, or those who lay no claim at all to their words. I happen to not do so.

So now, my RSS feed is excerpted with an irritating and stupidly long copyright notice mentioning no copying or reblogging so even the IP-rights-impaired should be able to understand my wishes. Now, whether or not they are honored is another thing altogether.
</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure how much more of a niche area in which one can participate than the world of performing magicians and mindreaders. So you can imagine my surprise and irritation to find a guy reblogging the feed from Escamoteurettes. (Even though my copyright notice is fairly plain in language.)</p>
<p>It took three days, several phone calls, and a number of emails before I found the owner of the site (thanks, whoever you are, who came up with the brilliant idea of proxy registrations) and convinced him I was dead serious about him ceasing from republishing my stuff.</p>
<p>The Reader&#8217;s Digest version of the story is I was called a luddite for not embracing reblogging. &#8220;Why would I not want my content republished?&#8221; Uh, maybe because I&#8217;d rather visitors to my web site to read my content there? Maybe I have something of a problem with someone republishing my work &#8212; insignificant as it is, it&#8217;s still my work &#8212; and not even bother to credit me or provide a link back to my web site, let alone ask my permission?</p>
<p>Yes, I know it&#8217;s a bit like two ants fighting for a crumb of bread. But to the ant, it&#8217;s a pretty big thing.</p>
<p>I applaud those who publish under the Creative Commons license, or those who lay no claim at all to their words. I happen to not do so.</p>
<p>So now, my RSS feed is excerpted with an irritating and stupidly long copyright notice mentioning no copying or reblogging so even the IP-rights-impaired should be able to understand my wishes. Now, whether or not they are honored is another thing altogether.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Short</title>
		<link>http://www.blogherald.com/2005/06/01/content-theft-on-the-rise-what-now-scoble/comment-page-1/#comment-29413</link>
		<dc:creator>Paul Short</dc:creator>
		<pubDate>Wed, 01 Jun 2005 04:50:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2005/06/01/content-theft-on-the-rise-what-now-scoble/#comment-29413</guid>
		<description>Duncan, I&#039;ve done a little hacking of the wp-rss2.php file and found a way to add a copyright notice right in the excerpts themselves. It says something to the effect of:

&lt;i&gt;(C) 2005 Blogherald.com If you&#039;re not reading this in your news aggregator, this material has been stolen. Please contact editor at blogherald.com so we can take immediate legal action.&lt;/i&gt;

The beauty of it though, is that it&#039;s part of the content of the excerpt itself, so that message shows up right on the offenders web page. ;-)</description>
		<content:encoded><![CDATA[<p>Duncan, I&#8217;ve done a little hacking of the wp-rss2.php file and found a way to add a copyright notice right in the excerpts themselves. It says something to the effect of:</p>
<p><i>(C) 2005 Blogherald.com If you&#8217;re not reading this in your news aggregator, this material has been stolen. Please contact editor at blogherald.com so we can take immediate legal action.</i></p>
<p>The beauty of it though, is that it&#8217;s part of the content of the excerpt itself, so that message shows up right on the offenders web page. ;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The One True b!X</title>
		<link>http://www.blogherald.com/2005/06/01/content-theft-on-the-rise-what-now-scoble/comment-page-1/#comment-29410</link>
		<dc:creator>The One True b!X</dc:creator>
		<pubDate>Wed, 01 Jun 2005 03:43:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2005/06/01/content-theft-on-the-rise-what-now-scoble/#comment-29410</guid>
		<description>It&#039;s becoming increasingly irritating to me, all of this latest round of protestations against bloggers who provide excerpt-only RSS feeds.

Thing is, while that&#039;s the easiest way to steal people&#039;s content, it isn&#039;t the only way. Some time back, there was a site that was republishing full-text feeds, but if they couldn&#039;t find full-text &lt;em&gt;they would scrape the site&lt;/em&gt; and get the content that way. I caught them republishing my content that way and ultimately got them to remove it.

There&#039;s not much to be done to stop the scraping theft, but there&#039;s one easy way to stop theft-by-RSS: Excerpt-only feeds.</description>
		<content:encoded><![CDATA[<p>It&#8217;s becoming increasingly irritating to me, all of this latest round of protestations against bloggers who provide excerpt-only RSS feeds.</p>
<p>Thing is, while that&#8217;s the easiest way to steal people&#8217;s content, it isn&#8217;t the only way. Some time back, there was a site that was republishing full-text feeds, but if they couldn&#8217;t find full-text <em>they would scrape the site</em> and get the content that way. I caught them republishing my content that way and ultimately got them to remove it.</p>
<p>There&#8217;s not much to be done to stop the scraping theft, but there&#8217;s one easy way to stop theft-by-RSS: Excerpt-only feeds.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

