<?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: Plagiarists Blog Off!</title>
	<atom:link href="http://www.out-smarts.com/2008/03/14/plagiarists-blog-off/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.out-smarts.com/2008/03/14/plagiarists-blog-off/</link>
	<description>Smart social media marketing strategies and services that maximise Internet exposure.</description>
	<lastBuildDate>Thu, 04 Mar 2010 07:19:48 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: M. Thomas Eisenstadt&#8217;s Blog &#187; Blog Archive &#187; Eliot Spitzer Plagiarizes in Resignation Speech</title>
		<link>http://www.out-smarts.com/2008/03/14/plagiarists-blog-off/comment-page-1/#comment-135</link>
		<dc:creator>M. Thomas Eisenstadt&#8217;s Blog &#187; Blog Archive &#187; Eliot Spitzer Plagiarizes in Resignation Speech</dc:creator>
		<pubDate>Fri, 14 Mar 2008 20:31:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.out-smarts.com/2008/03/14/plagiarists-blog-off/#comment-135</guid>
		<description>[...] and &#8220;misappropriation&#8221; of quotes. The lesson is, when there&#8217;s a dispute, then attribute. But maybe Eliot Spitzer should have been reading the blog. In his resignation speech the other [...]</description>
		<content:encoded><![CDATA[<p>[...] and &#8220;misappropriation&#8221; of quotes. The lesson is, when there&#8217;s a dispute, then attribute. But maybe Eliot Spitzer should have been reading the blog. In his resignation speech the other [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Bailey</title>
		<link>http://www.out-smarts.com/2008/03/14/plagiarists-blog-off/comment-page-1/#comment-134</link>
		<dc:creator>Jonathan Bailey</dc:creator>
		<pubDate>Fri, 14 Mar 2008 19:47:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.out-smarts.com/2008/03/14/plagiarists-blog-off/#comment-134</guid>
		<description>Ok, there&#039;s a lot to talk about here so I&#039;ll jump right in.

When you talk about what to do next, I&#039;ll assume you&#039;re talking about if the person had not removed the work. With the post gone you can&#039;t do much other than laugh at the reply they sent.

If they hadn&#039;t removed the post, the next step would have been to file a DMCA notice with the host and get them to remove it for you. A DMCA notice works with hosts in the U.S. and hosts in the EU, Australia and elsewhere have similar laws. It requires hosts to remove infringing material or, potentially, be held liable for the infringement.

Needless to say, hosts are very responsive to that.

If you need, you can find stock letters on my site.

If that had failed, you could try a similar tact but get the site deindexed from the search engines with the same method. That almost always is a success.

As far as ways to guard against that type of abuse. There are many but without knowing the details of the case it is hard to give a good solution for it.

Since most of the content theft involves RSS feeds, there are many good plugins that can help RSS scraping including plugins to add digital fingerprints for copy tracking, plugins to redirect scrapers to a false feed and everything in between.

Regarding hand content theft, your best bet is still Google and Google Alerts. But there are new tools coming down the pipe soon. Stay tuned.

In the meantime, try using Copyscape or Bitscan to see if they can find copies of your work. Both are at least fairly effective at tracking down plagiarists.

Hope that this helps and let me know if there is anything I can do!</description>
		<content:encoded><![CDATA[<p>Ok, there&#8217;s a lot to talk about here so I&#8217;ll jump right in.</p>
<p>When you talk about what to do next, I&#8217;ll assume you&#8217;re talking about if the person had not removed the work. With the post gone you can&#8217;t do much other than laugh at the reply they sent.</p>
<p>If they hadn&#8217;t removed the post, the next step would have been to file a DMCA notice with the host and get them to remove it for you. A DMCA notice works with hosts in the U.S. and hosts in the EU, Australia and elsewhere have similar laws. It requires hosts to remove infringing material or, potentially, be held liable for the infringement.</p>
<p>Needless to say, hosts are very responsive to that.</p>
<p>If you need, you can find stock letters on my site.</p>
<p>If that had failed, you could try a similar tact but get the site deindexed from the search engines with the same method. That almost always is a success.</p>
<p>As far as ways to guard against that type of abuse. There are many but without knowing the details of the case it is hard to give a good solution for it.</p>
<p>Since most of the content theft involves RSS feeds, there are many good plugins that can help RSS scraping including plugins to add digital fingerprints for copy tracking, plugins to redirect scrapers to a false feed and everything in between.</p>
<p>Regarding hand content theft, your best bet is still Google and Google Alerts. But there are new tools coming down the pipe soon. Stay tuned.</p>
<p>In the meantime, try using Copyscape or Bitscan to see if they can find copies of your work. Both are at least fairly effective at tracking down plagiarists.</p>
<p>Hope that this helps and let me know if there is anything I can do!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Beaty</title>
		<link>http://www.out-smarts.com/2008/03/14/plagiarists-blog-off/comment-page-1/#comment-133</link>
		<dc:creator>Bob Beaty</dc:creator>
		<pubDate>Fri, 14 Mar 2008 18:19:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.out-smarts.com/2008/03/14/plagiarists-blog-off/#comment-133</guid>
		<description>Much like pet ownership there are no rules for blogging. In a quest to keep a blog current, folks will try--or steal--just about anything. The hell of it, linking can accomplish the same thing and extend the discussion. About the only thing one can do is to ask for credit or the info be removed. Personally, I would probably publish the incident and the response. Calling a coward--or plagiarist-- out usually results in setting the tone for now and in the future. 

I find that these people usually don&#039;t last long as if made a practice, folks much less forgiving than you will make their life a misery. And once that happens, the blog usually disappears.

The one good thing about the internet is that it keeps these mooks off the street. The bad thing is it gives them a voice. Hopefully as blogging and SM gains traction, it will self police.

Happened with chatrooms and message boards, so confidence remains high.

Remain an advocate. And take no prisoners...</description>
		<content:encoded><![CDATA[<p>Much like pet ownership there are no rules for blogging. In a quest to keep a blog current, folks will try&#8211;or steal&#8211;just about anything. The hell of it, linking can accomplish the same thing and extend the discussion. About the only thing one can do is to ask for credit or the info be removed. Personally, I would probably publish the incident and the response. Calling a coward&#8211;or plagiarist&#8211; out usually results in setting the tone for now and in the future. </p>
<p>I find that these people usually don&#8217;t last long as if made a practice, folks much less forgiving than you will make their life a misery. And once that happens, the blog usually disappears.</p>
<p>The one good thing about the internet is that it keeps these mooks off the street. The bad thing is it gives them a voice. Hopefully as blogging and SM gains traction, it will self police.</p>
<p>Happened with chatrooms and message boards, so confidence remains high.</p>
<p>Remain an advocate. And take no prisoners&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
