<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Unattributed copying of perl blog content via Planet Perl</title>
	<atom:link href="http://blog.timbunce.org/2009/06/15/unattributed-copying-of-perl-blog-content-via-planet-perl/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.timbunce.org/2009/06/15/unattributed-copying-of-perl-blog-content-via-planet-perl/</link>
	<description>Listen. Reflect. Explore. Solve.</description>
	<lastBuildDate>Tue, 02 Mar 2010 15:29:41 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: TimBunce</title>
		<link>http://blog.timbunce.org/2009/06/15/unattributed-copying-of-perl-blog-content-via-planet-perl/#comment-1252</link>
		<dc:creator>TimBunce</dc:creator>
		<pubDate>Tue, 29 Sep 2009 08:51:22 +0000</pubDate>
		<guid isPermaLink="false">http://timbunce.wordpress.com/?p=282#comment-1252</guid>
		<description>I had started an email discussion with them just after I wrote the post. They were willing to give better attribution, and, after a little back-and-forth they&#039;d updated their template to include a link to the original article and where they got it from, i.e., planet perl. I was happy enough with that. Kudos to them for being open to making these changes.

Now I come to look again (prompted by http://mdk.per.ly/2009/09/28/coming-soon-planet-perl-archives/) I see they&#039;ve taken down that content and are no longer republishing the planet perl feed.</description>
		<content:encoded><![CDATA[<p>I had started an email discussion with them just after I wrote the post. They were willing to give better attribution, and, after a little back-and-forth they&#8217;d updated their template to include a link to the original article and where they got it from, i.e., planet perl. I was happy enough with that. Kudos to them for being open to making these changes.</p>
<p>Now I come to look again (prompted by <a href="http://mdk.per.ly/2009/09/28/coming-soon-planet-perl-archives/)" rel="nofollow">http://mdk.per.ly/2009/09/28/coming-soon-planet-perl-archives/)</a> I see they&#8217;ve taken down that content and are no longer republishing the planet perl feed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabor Szabo</title>
		<link>http://blog.timbunce.org/2009/06/15/unattributed-copying-of-perl-blog-content-via-planet-perl/#comment-953</link>
		<dc:creator>Gabor Szabo</dc:creator>
		<pubDate>Tue, 16 Jun 2009 03:53:45 +0000</pubDate>
		<guid isPermaLink="false">http://timbunce.wordpress.com/?p=282#comment-953</guid>
		<description>Have you tried sending an e-mail asking the person to remove your (or the perl planet) feed from his site? 
It might be worth a mail.

For some of my longer posts I write a short abstract of 3-5 lines and only that abstract goes in the feed with a link back to the original full article. I did this actually to avoid filling a planet with my 300 line long posts but it actually also solves the copying problem.</description>
		<content:encoded><![CDATA[<p>Have you tried sending an e-mail asking the person to remove your (or the perl planet) feed from his site?<br />
It might be worth a mail.</p>
<p>For some of my longer posts I write a short abstract of 3-5 lines and only that abstract goes in the feed with a link back to the original full article. I did this actually to avoid filling a planet with my 300 line long posts but it actually also solves the copying problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mekk</title>
		<link>http://blog.timbunce.org/2009/06/15/unattributed-copying-of-perl-blog-content-via-planet-perl/#comment-951</link>
		<dc:creator>Mekk</dc:creator>
		<pubDate>Mon, 15 Jun 2009 19:57:18 +0000</pubDate>
		<guid isPermaLink="false">http://timbunce.wordpress.com/?p=282#comment-951</guid>
		<description>While not always fully working, using Google Spam Report (there is special marker &quot;duplicate content&quot; there) makes attempts of those people far less useful</description>
		<content:encoded><![CDATA[<p>While not always fully working, using Google Spam Report (there is special marker &#8220;duplicate content&#8221; there) makes attempts of those people far less useful</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TimBunce</title>
		<link>http://blog.timbunce.org/2009/06/15/unattributed-copying-of-perl-blog-content-via-planet-perl/#comment-950</link>
		<dc:creator>TimBunce</dc:creator>
		<pubDate>Mon, 15 Jun 2009 19:42:17 +0000</pubDate>
		<guid isPermaLink="false">http://timbunce.wordpress.com/?p=282#comment-950</guid>
		<description>I&#039;m content to simply make it clear what my licence is so people copying at least know they&#039;re acting outside the licence. That is their choice, and I agree there&#039;s little I can do about it, but I want to be sure they know what they&#039;re doing and are making a conscious choice.

I like the approach taken by Rui Carmo for &lt;a href=&quot;http://the.taoofmac.com/&quot; rel=&quot;nofollow&quot;&gt;The Tao of Mac&lt;/a&gt;. His system automatically adds into the RSS feed, at the end of each post, text like the following: &lt;blockquote&gt;&quot;IMAP Scraping&quot; was written by Rui Carmo for The Tao of Mac and was originally posted on Tuesday, 3 January 2006. Except as noted, it&#039;s ©2009 Rui Carmo and licensed for reuse under CC BY-NC-ND 3.0.&lt;/blockquote&gt; and it&#039;s presented in a nice box with dark background. See http://feedproxy.google.com/taoofmac/blog for examples.

That&#039;s polite and understated, yet clearly conveys the authorship and licensing intent. Essentially he&#039;s building attribution into the feed itself. I imagine few redistributors would go to the trouble of removing it.

I might try doing something similar, though it&#039;ll have to appear on the main articles as well as the feed as I don&#039;t have as much control as Rui does - he built his own system wereas I&#039;m using wordpress.com.</description>
		<content:encoded><![CDATA[<p>I&#8217;m content to simply make it clear what my licence is so people copying at least know they&#8217;re acting outside the licence. That is their choice, and I agree there&#8217;s little I can do about it, but I want to be sure they know what they&#8217;re doing and are making a conscious choice.</p>
<p>I like the approach taken by Rui Carmo for <a href="http://the.taoofmac.com/" rel="nofollow">The Tao of Mac</a>. His system automatically adds into the RSS feed, at the end of each post, text like the following:<br />
<blockquote>&#8220;IMAP Scraping&#8221; was written by Rui Carmo for The Tao of Mac and was originally posted on Tuesday, 3 January 2006. Except as noted, it&#8217;s ©2009 Rui Carmo and licensed for reuse under CC BY-NC-ND 3.0.</p></blockquote>
<p> and it&#8217;s presented in a nice box with dark background. See <a href="http://feedproxy.google.com/taoofmac/blog" rel="nofollow">http://feedproxy.google.com/taoofmac/blog</a> for examples.</p>
<p>That&#8217;s polite and understated, yet clearly conveys the authorship and licensing intent. Essentially he&#8217;s building attribution into the feed itself. I imagine few redistributors would go to the trouble of removing it.</p>
<p>I might try doing something similar, though it&#8217;ll have to appear on the main articles as well as the feed as I don&#8217;t have as much control as Rui does &#8211; he built his own system wereas I&#8217;m using wordpress.com.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brian d foy</title>
		<link>http://blog.timbunce.org/2009/06/15/unattributed-copying-of-perl-blog-content-via-planet-perl/#comment-949</link>
		<dc:creator>brian d foy</dc:creator>
		<pubDate>Mon, 15 Jun 2009 17:10:25 +0000</pubDate>
		<guid isPermaLink="false">http://timbunce.wordpress.com/?p=282#comment-949</guid>
		<description>Licenses won&#039;t fix this sort of thing. People are going to steal your work to make ad attractors and there&#039;s no reasonable recourse for you. There are laws that could protect you, but only if you&#039;re willing to spend money on private legal resources. Even in the US, the DCMA is only useful as a 10 day injunction, after which it&#039;s a civil matter that you most privately pursue. The carriers are completely unwilling to get involved, and happily reinstatement infringing material once the injunction has expired.

What I have discovered, as well as many non-tech writers I know, is that it isn&#039;t worth writing on blogs when this sort of thing happens and there is no reasonable recourse. People scoff at the notion of a &quot;chilling effect&quot;, but it is definitely there. My google blogsearch results for my name and the title of my books are 90% this sort of crap. Now I just assume that anything I write is going to be stolen and there&#039;s nothing I can do to stop it. As such, I write a lot less. 

Some people are always going to break the rules as long as they think they are close to the line. I&#039;d like to support things like Creative Commons, but when you move the line farther out, it only moves the lengths people will go to infringe farther too.</description>
		<content:encoded><![CDATA[<p>Licenses won&#8217;t fix this sort of thing. People are going to steal your work to make ad attractors and there&#8217;s no reasonable recourse for you. There are laws that could protect you, but only if you&#8217;re willing to spend money on private legal resources. Even in the US, the DCMA is only useful as a 10 day injunction, after which it&#8217;s a civil matter that you most privately pursue. The carriers are completely unwilling to get involved, and happily reinstatement infringing material once the injunction has expired.</p>
<p>What I have discovered, as well as many non-tech writers I know, is that it isn&#8217;t worth writing on blogs when this sort of thing happens and there is no reasonable recourse. People scoff at the notion of a &#8220;chilling effect&#8221;, but it is definitely there. My google blogsearch results for my name and the title of my books are 90% this sort of crap. Now I just assume that anything I write is going to be stolen and there&#8217;s nothing I can do to stop it. As such, I write a lot less. </p>
<p>Some people are always going to break the rules as long as they think they are close to the line. I&#8217;d like to support things like Creative Commons, but when you move the line farther out, it only moves the lengths people will go to infringe farther too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: john napiorkowski</title>
		<link>http://blog.timbunce.org/2009/06/15/unattributed-copying-of-perl-blog-content-via-planet-perl/#comment-946</link>
		<dc:creator>john napiorkowski</dc:creator>
		<pubDate>Mon, 15 Jun 2009 12:50:16 +0000</pubDate>
		<guid isPermaLink="false">http://timbunce.wordpress.com/?p=282#comment-946</guid>
		<description>This is a great idea.  I&#039;m going to start adding some stuff to the bottom of my blogs and will make the license part of it going forward.</description>
		<content:encoded><![CDATA[<p>This is a great idea.  I&#8217;m going to start adding some stuff to the bottom of my blogs and will make the license part of it going forward.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
