<?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: Copyright violation &amp; blogging: a tricky subject</title>
	<atom:link href="http://www.almostgotit.com/2007/05/21/copyright-violation-blogging-a-tricky-subject/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.almostgotit.com/2007/05/21/copyright-violation-blogging-a-tricky-subject/</link>
	<description>So, kids are mostly raised &#38; I&#039;ve just gone back to work...</description>
	<lastBuildDate>Tue, 03 May 2011 14:46:12 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Almostgotit.com &#124; 2008 &#124; August &#124; 20</title>
		<link>http://www.almostgotit.com/2007/05/21/copyright-violation-blogging-a-tricky-subject/comment-page-1/#comment-1595</link>
		<dc:creator>Almostgotit.com &#124; 2008 &#124; August &#124; 20</dc:creator>
		<pubDate>Wed, 20 Aug 2008 17:49:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.almostgotit.com/?p=206#comment-1595</guid>
		<description>[...] who should own the rights to your comments: you or the blog where you&#8217;ve left them?  ( Copyright protocols and blogging continue to [...]</description>
		<content:encoded><![CDATA[<p>[...] who should own the rights to your comments: you or the blog where you&#8217;ve left them?  ( Copyright protocols and blogging continue to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Almostgotit.com &#124; DISQUS &#38; CommentLuv</title>
		<link>http://www.almostgotit.com/2007/05/21/copyright-violation-blogging-a-tricky-subject/comment-page-1/#comment-1594</link>
		<dc:creator>Almostgotit.com &#124; DISQUS &#38; CommentLuv</dc:creator>
		<pubDate>Wed, 20 Aug 2008 17:46:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.almostgotit.com/?p=206#comment-1594</guid>
		<description>[...] who should own the rights to your comments: you or the blog where you&#8217;ve left them?  ( Copyright protocols and blogging continue to [...]</description>
		<content:encoded><![CDATA[<p>[...] who should own the rights to your comments: you or the blog where you&#8217;ve left them?  ( Copyright protocols and blogging continue to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: almostgotit</title>
		<link>http://www.almostgotit.com/2007/05/21/copyright-violation-blogging-a-tricky-subject/comment-page-1/#comment-428</link>
		<dc:creator>almostgotit</dc:creator>
		<pubDate>Thu, 24 May 2007 16:30:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.almostgotit.com/?p=206#comment-428</guid>
		<description>I wasn&#039;t clear, sorry: the spam is unrelated to the other incident.  The spam is the &quot;Viagra &amp; nude hotties&quot; type of stuff, and it is being submitted to my blog, by spam robots, as comments on my posts. It really only started to appear a few days ago -- probably because my blog is still relatively new.  I was told to expect it eventually, though... like termites, spam is not an &quot;if&quot; but a &quot;when.&quot;   Fortunately, the Akismet feature (a default on Wordpress.com!!)  has intercepted them all so far, and the fact that I must approve comments before they appear is the final fail-safe.
Some blogs collect ad revenue legitimately, using the blogger&#039;s own content. (though many free blog hosts, including this one, don&#039;t allow ads.) The BAD blogs are those set up with random chunks of &quot;scraped&quot; (stolen) content just to support the ads.   Scams, in other words.  Note:  &lt;a&gt;GoogleAds &lt;/a&gt;is on to these folks, and they patrol the sites using their ads.  They also have a system for reporting violations.  I am impressed at how fast they pulled their ads off this one!  The site is still up, however, and seems to be soliciting.

Anyone more experienced than I want to weigh in with more insight on any of this?</description>
		<content:encoded><![CDATA[<p>I wasn&#8217;t clear, sorry: the spam is unrelated to the other incident.  The spam is the &#8220;Viagra &amp; nude hotties&#8221; type of stuff, and it is being submitted to my blog, by spam robots, as comments on my posts. It really only started to appear a few days ago &#8212; probably because my blog is still relatively new.  I was told to expect it eventually, though&#8230; like termites, spam is not an &#8220;if&#8221; but a &#8220;when.&#8221;   Fortunately, the Akismet feature (a default on Wordpress.com!!)  has intercepted them all so far, and the fact that I must approve comments before they appear is the final fail-safe.<br />
Some blogs collect ad revenue legitimately, using the blogger&#8217;s own content. (though many free blog hosts, including this one, don&#8217;t allow ads.) The BAD blogs are those set up with random chunks of &#8220;scraped&#8221; (stolen) content just to support the ads.   Scams, in other words.  Note:  <a>GoogleAds </a>is on to these folks, and they patrol the sites using their ads.  They also have a system for reporting violations.  I am impressed at how fast they pulled their ads off this one!  The site is still up, however, and seems to be soliciting.</p>
<p>Anyone more experienced than I want to weigh in with more insight on any of this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rockyroadoflove</title>
		<link>http://www.almostgotit.com/2007/05/21/copyright-violation-blogging-a-tricky-subject/comment-page-1/#comment-427</link>
		<dc:creator>rockyroadoflove</dc:creator>
		<pubDate>Thu, 24 May 2007 15:01:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.almostgotit.com/?p=206#comment-427</guid>
		<description>Goodness! I&#039;m such a novice still. What&#039;s a spam comment count? Do you mean the website traced you from your complaints about them? I want readers to copy my recipes for themselves. That&#039;s the whole point of a cooking blog. Should I add a line to my copyright blurb saying copying for personal use is encouraged? It&#039;s the re-publication rights I want to control.</description>
		<content:encoded><![CDATA[<p>Goodness! I&#8217;m such a novice still. What&#8217;s a spam comment count? Do you mean the website traced you from your complaints about them? I want readers to copy my recipes for themselves. That&#8217;s the whole point of a cooking blog. Should I add a line to my copyright blurb saying copying for personal use is encouraged? It&#8217;s the re-publication rights I want to control.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: almostgotit</title>
		<link>http://www.almostgotit.com/2007/05/21/copyright-violation-blogging-a-tricky-subject/comment-page-1/#comment-429</link>
		<dc:creator>almostgotit</dc:creator>
		<pubDate>Thu, 24 May 2007 00:05:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.almostgotit.com/?p=206#comment-429</guid>
		<description>This happens, too:
I just wrote a post and found it a few minutes later posted on a site called http://thatsthenewthing.com/, which is clearly set up to scrape other people&#039;s content and profit from associated GoogleAds revenue.   My stats counter clued me in with a link from their site.  I reported it to GoogleAds using their &quot;violations&quot; form, and also posted a comment to the blog itself informing them it was copyrighted material and was to be removed immediately.  I imagine this site will be gone by morning and they&#039;ll set up a new one...

(next morning update):  The site&#039;s still up, but both my content AND GoogleAds are now gone.  A giant Blockbuster ad is still there, but I clicked through and reported the violation to Blockbuster, also (and they are liable, too, so long as they continue sponsoring the site.)  Finally, I found the owner of the content CURRENTLY posted (where mine was yesterday) and gave them a head&#039;s up.

Meanwhile, my own blog&#039;s spam comment count has just shot up, too... they&#039;ve FOUND me.
Welcome to the Blogosphere, folks.</description>
		<content:encoded><![CDATA[<p>This happens, too:<br />
I just wrote a post and found it a few minutes later posted on a site called <a href="http://thatsthenewthing.com/" rel="nofollow">http://thatsthenewthing.com/</a>, which is clearly set up to scrape other people&#8217;s content and profit from associated GoogleAds revenue.   My stats counter clued me in with a link from their site.  I reported it to GoogleAds using their &#8220;violations&#8221; form, and also posted a comment to the blog itself informing them it was copyrighted material and was to be removed immediately.  I imagine this site will be gone by morning and they&#8217;ll set up a new one&#8230;</p>
<p>(next morning update):  The site&#8217;s still up, but both my content AND GoogleAds are now gone.  A giant Blockbuster ad is still there, but I clicked through and reported the violation to Blockbuster, also (and they are liable, too, so long as they continue sponsoring the site.)  Finally, I found the owner of the content CURRENTLY posted (where mine was yesterday) and gave them a head&#8217;s up.</p>
<p>Meanwhile, my own blog&#8217;s spam comment count has just shot up, too&#8230; they&#8217;ve FOUND me.<br />
Welcome to the Blogosphere, folks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: almostgotit</title>
		<link>http://www.almostgotit.com/2007/05/21/copyright-violation-blogging-a-tricky-subject/comment-page-1/#comment-430</link>
		<dc:creator>almostgotit</dc:creator>
		<pubDate>Tue, 22 May 2007 21:18:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.almostgotit.com/?p=206#comment-430</guid>
		<description>Thank you both so much for these comments.  Mcory1 has hit upon a prudent way of largely avoiding the issue, I think, and also provided the insight of &quot;if it were my material...&quot;  which is perhaps the most helpful perspective of all when thinking through these things.  &quot;Do unto others,&quot; etc.
And rockyroadoflove, you continue to be such an inspiration (not to mention knowledge-source!) for me.  (I should add that Rocky is a fellow refugee from The Institution Which Shall Not be Named... and may never know how inspirational she has been on that front, as well!)</description>
		<content:encoded><![CDATA[<p>Thank you both so much for these comments.  Mcory1 has hit upon a prudent way of largely avoiding the issue, I think, and also provided the insight of &#8220;if it were my material&#8230;&#8221;  which is perhaps the most helpful perspective of all when thinking through these things.  &#8220;Do unto others,&#8221; etc.<br />
And rockyroadoflove, you continue to be such an inspiration (not to mention knowledge-source!) for me.  (I should add that Rocky is a fellow refugee from The Institution Which Shall Not be Named&#8230; and may never know how inspirational she has been on that front, as well!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rockyroadoflove</title>
		<link>http://www.almostgotit.com/2007/05/21/copyright-violation-blogging-a-tricky-subject/comment-page-1/#comment-432</link>
		<dc:creator>rockyroadoflove</dc:creator>
		<pubDate>Tue, 22 May 2007 18:26:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.almostgotit.com/?p=206#comment-432</guid>
		<description>Plagiarism, no matter where you find it, is stealing someone else&#039;s work and presenting it as your own. Quoting from or paraphrasing other writers, with attribution and links, is, to my way of thinking, what makes the Web so rich and interconnected. Printing a line you can&#039;t remember the source of and asking if anyone else knows where it came from is not plagiarism—it&#039;s a query. I would be very pleased if someone quoted from my blog with credit and a link, of course. I print my own recipes on my blog, and the only copyrightable part of a recipe is the form in which it&#039;s written. You can&#039;t sue someone because they, too, put celery seeds in pimiento cheese. Maida Heatter&#039;s famous brownie recipe from the 1980s is nothing more than Irma Rombauer&#039;s 1930s recipe doubled.

Images, though, are different from words. It&#039;s not just that you rarely use part of an image. The problem of using a copyrighted image without permission is that you might reprint it incorrectly—minus some layers, with a skewed color palette or pixels—so that it&#039;s not at all what the photographer or artist intended. The photographer who takes the food shots for my blog taught me how to prepare originals for the Web so that all the layers are included and the color is right and the cropping. We even made a template with a copyright line that&#039;s a permanent part of the image. Someone could lift a photo and pretend it&#039;s theirs. But a public record with a copyright line is all the legal protection you need—or can get.

All that said, I do hope that if someone steals my words my Copyscape protection will spot them on the Web. Computerized tracing works with music. iTunes is what brought down Joyce Hatto, the plagiarizing British pianist.</description>
		<content:encoded><![CDATA[<p>Plagiarism, no matter where you find it, is stealing someone else&#8217;s work and presenting it as your own. Quoting from or paraphrasing other writers, with attribution and links, is, to my way of thinking, what makes the Web so rich and interconnected. Printing a line you can&#8217;t remember the source of and asking if anyone else knows where it came from is not plagiarism—it&#8217;s a query. I would be very pleased if someone quoted from my blog with credit and a link, of course. I print my own recipes on my blog, and the only copyrightable part of a recipe is the form in which it&#8217;s written. You can&#8217;t sue someone because they, too, put celery seeds in pimiento cheese. Maida Heatter&#8217;s famous brownie recipe from the 1980s is nothing more than Irma Rombauer&#8217;s 1930s recipe doubled.</p>
<p>Images, though, are different from words. It&#8217;s not just that you rarely use part of an image. The problem of using a copyrighted image without permission is that you might reprint it incorrectly—minus some layers, with a skewed color palette or pixels—so that it&#8217;s not at all what the photographer or artist intended. The photographer who takes the food shots for my blog taught me how to prepare originals for the Web so that all the layers are included and the color is right and the cropping. We even made a template with a copyright line that&#8217;s a permanent part of the image. Someone could lift a photo and pretend it&#8217;s theirs. But a public record with a copyright line is all the legal protection you need—or can get.</p>
<p>All that said, I do hope that if someone steals my words my Copyscape protection will spot them on the Web. Computerized tracing works with music. iTunes is what brought down Joyce Hatto, the plagiarizing British pianist.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mcory1</title>
		<link>http://www.almostgotit.com/2007/05/21/copyright-violation-blogging-a-tricky-subject/comment-page-1/#comment-431</link>
		<dc:creator>mcory1</dc:creator>
		<pubDate>Tue, 22 May 2007 12:19:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.almostgotit.com/?p=206#comment-431</guid>
		<description>My personal opinion: plagiarism and copyright are really &quot;in the eye of the beholder&quot;, unless you&#039;re dealing with stuff that&#039;s exclusively and overtly protected.  When I can (and it hasn&#039;t been an issue yet on my blog), I try to cite a source for a quote and at least give a link; if I can&#039;t remember who it is, I forgo the quote -- that&#039;s why it hasn&#039;t been an issue for me yet.  Just easier to figure something else out than to worry about getting it right.

If it were my material, I&#039;d prefer just a link and an attribution -- the link mainly because I can always use the extra traffic.  I&#039;m sure there&#039;s a lot of people who don&#039;t care at all, and a lot of people who&#039;d jump at the chance to sue someone for using a couple of sentences from a blog or a picture that everyone else seems to be downloading too.</description>
		<content:encoded><![CDATA[<p>My personal opinion: plagiarism and copyright are really &#8220;in the eye of the beholder&#8221;, unless you&#8217;re dealing with stuff that&#8217;s exclusively and overtly protected.  When I can (and it hasn&#8217;t been an issue yet on my blog), I try to cite a source for a quote and at least give a link; if I can&#8217;t remember who it is, I forgo the quote &#8212; that&#8217;s why it hasn&#8217;t been an issue for me yet.  Just easier to figure something else out than to worry about getting it right.</p>
<p>If it were my material, I&#8217;d prefer just a link and an attribution &#8212; the link mainly because I can always use the extra traffic.  I&#8217;m sure there&#8217;s a lot of people who don&#8217;t care at all, and a lot of people who&#8217;d jump at the chance to sue someone for using a couple of sentences from a blog or a picture that everyone else seems to be downloading too.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

