<?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: The Plague of Plagiarism</title>
	<atom:link href="http://sqlchicken.com/2010/01/the-plague-of-plagiarism/feed/" rel="self" type="application/rss+xml" />
	<link>http://sqlchicken.com/2010/01/the-plague-of-plagiarism/</link>
	<description>SQL Server DBA Tips &#38; Tricks</description>
	<lastBuildDate>Tue, 15 May 2012 18:59:45 -0400</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Greg</title>
		<link>http://sqlchicken.com/2010/01/the-plague-of-plagiarism/comment-page-1/#comment-1731</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Tue, 09 Nov 2010 20:56:09 +0000</pubDate>
		<guid isPermaLink="false">http://sqlchicken.com/?p=533#comment-1731</guid>
		<description>True points, I agree there is probably some level of protection always. But really, the idea of this data protectionism is somewhat dated. These days everything is interconnected to everything else. If it&#039;s not, then it&#039;s privatized to some degree, such as having member login etc.

But yes it is wrong not to link back, that is the area the &quot;heat&quot; should be focused on - saying &quot;hey dude, add this single parameter to your spidering: our linkback URL.

The thread should be called the-plague-of-not-linking-back, as that is what really bothered everyone to begin with. I&#039;m sure you don&#039;t mind your work being all over the internet, but as long as the credit was given in a bit more of an expressive and direct way.

look up any troubleshooting topic online. See how many sites are really just compilations of useful content spidered from many other sites. They don&#039;t even put any linkbacks, they just archive and display the content.  But it helps people find the content. It is a positive thing, right? If you think your content is so valuable and needs to be protected, print a book and sell it. Otherwise, be happy that your BLOGS are being read and used. If some jackme thinks it&#039;s cool to jack your posts, well he&#039;s the one losing out in the end...

IF that is what he&#039;s doing. Which he&#039;s not.

just sayin&#039;</description>
		<content:encoded><![CDATA[<p>True points, I agree there is probably some level of protection always. But really, the idea of this data protectionism is somewhat dated. These days everything is interconnected to everything else. If it&#8217;s not, then it&#8217;s privatized to some degree, such as having member login etc.</p>
<p>But yes it is wrong not to link back, that is the area the &#8220;heat&#8221; should be focused on &#8211; saying &#8220;hey dude, add this single parameter to your spidering: our linkback URL.</p>
<p>The thread should be called the-plague-of-not-linking-back, as that is what really bothered everyone to begin with. I&#8217;m sure you don&#8217;t mind your work being all over the internet, but as long as the credit was given in a bit more of an expressive and direct way.</p>
<p>look up any troubleshooting topic online. See how many sites are really just compilations of useful content spidered from many other sites. They don&#8217;t even put any linkbacks, they just archive and display the content.  But it helps people find the content. It is a positive thing, right? If you think your content is so valuable and needs to be protected, print a book and sell it. Otherwise, be happy that your BLOGS are being read and used. If some jackme thinks it&#8217;s cool to jack your posts, well he&#8217;s the one losing out in the end&#8230;</p>
<p>IF that is what he&#8217;s doing. Which he&#8217;s not.</p>
<p>just sayin&#8217;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed Leighton-Dick</title>
		<link>http://sqlchicken.com/2010/01/the-plague-of-plagiarism/comment-page-1/#comment-1728</link>
		<dc:creator>Ed Leighton-Dick</dc:creator>
		<pubDate>Tue, 09 Nov 2010 14:54:13 +0000</pubDate>
		<guid isPermaLink="false">http://sqlchicken.com/?p=533#comment-1728</guid>
		<description>You&#039;re wrong on your third point. As soon as you put something into any sort of tangible form, it&#039;s protected by copyright. This iincludes the Internet. Registering the copyright strengthens the protection, but it still exists.</description>
		<content:encoded><![CDATA[<p>You&#8217;re wrong on your third point. As soon as you put something into any sort of tangible form, it&#8217;s protected by copyright. This iincludes the Internet. Registering the copyright strengthens the protection, but it still exists.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ferox11</title>
		<link>http://sqlchicken.com/2010/01/the-plague-of-plagiarism/comment-page-1/#comment-1727</link>
		<dc:creator>ferox11</dc:creator>
		<pubDate>Tue, 09 Nov 2010 14:21:56 +0000</pubDate>
		<guid isPermaLink="false">http://sqlchicken.com/?p=533#comment-1727</guid>
		<description>Plagerism sucks. Showing someone elses work with out linking back and crediting it to them sucks. Its hard putting out good content and it hurts if someone is jacking your hard work and then not giving you credit. I am appreciative of any community that helps curb plagerism. It hurts everyone by making content providers not want to provide content.</description>
		<content:encoded><![CDATA[<p>Plagerism sucks. Showing someone elses work with out linking back and crediting it to them sucks. Its hard putting out good content and it hurts if someone is jacking your hard work and then not giving you credit. I am appreciative of any community that helps curb plagerism. It hurts everyone by making content providers not want to provide content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jorge Segarra</title>
		<link>http://sqlchicken.com/2010/01/the-plague-of-plagiarism/comment-page-1/#comment-1726</link>
		<dc:creator>Jorge Segarra</dc:creator>
		<pubDate>Tue, 09 Nov 2010 14:13:22 +0000</pubDate>
		<guid isPermaLink="false">http://sqlchicken.com/?p=533#comment-1726</guid>
		<description>I&#039;m sorry but you&#039;re wrong. Google isn&#039;t reposting your work and passing it off as its own. And if you want a search engine to not index your pages its simply a matter of tweaking a setting on a page. When someone re-syndicates your content (via RSS for example) the first reaction typically is to tell the person to knock it off (or at least ask permission from the author first). Also as I mentioned before much of the content published on the web is covered by a license type of some type so syndicating without express permission violates those licenses. 

As for it being heated, the SQL community takes plagiarism very seriously as folks who write take a lot of time and effort to put together that content so its a little disconcerting when someone rips it off of you and tries to pass it off as their own (intentionally or not). Honestly, I&#039;m not sure why you&#039;re trying to justify plagiarism as a valid medium because it&#039;s not, it&#039;s theft.</description>
		<content:encoded><![CDATA[<p>I&#8217;m sorry but you&#8217;re wrong. Google isn&#8217;t reposting your work and passing it off as its own. And if you want a search engine to not index your pages its simply a matter of tweaking a setting on a page. When someone re-syndicates your content (via RSS for example) the first reaction typically is to tell the person to knock it off (or at least ask permission from the author first). Also as I mentioned before much of the content published on the web is covered by a license type of some type so syndicating without express permission violates those licenses. </p>
<p>As for it being heated, the SQL community takes plagiarism very seriously as folks who write take a lot of time and effort to put together that content so its a little disconcerting when someone rips it off of you and tries to pass it off as their own (intentionally or not). Honestly, I&#8217;m not sure why you&#8217;re trying to justify plagiarism as a valid medium because it&#8217;s not, it&#8217;s theft.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg</title>
		<link>http://sqlchicken.com/2010/01/the-plague-of-plagiarism/comment-page-1/#comment-1725</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Tue, 09 Nov 2010 14:09:28 +0000</pubDate>
		<guid isPermaLink="false">http://sqlchicken.com/?p=533#comment-1725</guid>
		<description>PS, do you have a link to this site that was indexing the content? I think it may be a quite useful site and would like to check it out.  :-)</description>
		<content:encoded><![CDATA[<p>PS, do you have a link to this site that was indexing the content? I think it may be a quite useful site and would like to check it out.  <img src='http://sqlchicken.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg</title>
		<link>http://sqlchicken.com/2010/01/the-plague-of-plagiarism/comment-page-1/#comment-1724</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Tue, 09 Nov 2010 14:07:38 +0000</pubDate>
		<guid isPermaLink="false">http://sqlchicken.com/?p=533#comment-1724</guid>
		<description>True that plagiarism is wrong, but I think you guys may be jumping on the bandwagon and having a crusade over the idea of plagiarism instead of looking at what this guy was doing.

Taking other&#039;s work, and making it seem it is your own personal work, that is plagiarism.

Indexing the publicly available content from other websites is not exactly plagiarism. If it was, would google also be guilty of this?

Perhaps he could have engineered his site better to include the URL of the posts he was indexing, infact I would have most definitely done that if I was him.

But just seems a bit heated. As I read on one of the responses, the copying of your work verbatim often increases traffic to your site, so in many ways the fact that someone finds your BLOG contributions worth reading and even worth copying is a positive indicator of how well your blog is doing. And it most likely will do even better based on people doing things like this.</description>
		<content:encoded><![CDATA[<p>True that plagiarism is wrong, but I think you guys may be jumping on the bandwagon and having a crusade over the idea of plagiarism instead of looking at what this guy was doing.</p>
<p>Taking other&#8217;s work, and making it seem it is your own personal work, that is plagiarism.</p>
<p>Indexing the publicly available content from other websites is not exactly plagiarism. If it was, would google also be guilty of this?</p>
<p>Perhaps he could have engineered his site better to include the URL of the posts he was indexing, infact I would have most definitely done that if I was him.</p>
<p>But just seems a bit heated. As I read on one of the responses, the copying of your work verbatim often increases traffic to your site, so in many ways the fact that someone finds your BLOG contributions worth reading and even worth copying is a positive indicator of how well your blog is doing. And it most likely will do even better based on people doing things like this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jorge Segarra</title>
		<link>http://sqlchicken.com/2010/01/the-plague-of-plagiarism/comment-page-1/#comment-1715</link>
		<dc:creator>Jorge Segarra</dc:creator>
		<pubDate>Mon, 08 Nov 2010 17:05:39 +0000</pubDate>
		<guid isPermaLink="false">http://sqlchicken.com/?p=533#comment-1715</guid>
		<description>Thanks for your feedback but I have disagree with you. The solution isn&#039;t to NOT post information publicly. If that were the case people should stop writing books, close down the internet and only talk to themselves! Most blogs are covered under Creative Commons license (http://www.google.com/search?sourceid=chrome&amp;ie=UTF-8&amp;q=creative+commons). Also, if you&#039;ve been in any sort of education system you know what plagiarism is and why it&#039;s wrong and you shouldn&#039;t do it. A blog, while not necessarily a revenue generator, is still someone&#039;s work. How would you like it if I came to your house and took your car even though you worked to pay it off. It&#039;s theft!</description>
		<content:encoded><![CDATA[<p>Thanks for your feedback but I have disagree with you. The solution isn&#8217;t to NOT post information publicly. If that were the case people should stop writing books, close down the internet and only talk to themselves! Most blogs are covered under Creative Commons license (<a href="http://www.google.com/search?sourceid=chrome&#038;ie=UTF-8&#038;q=creative+commons" rel="nofollow">http://www.google.com/search?sourceid=chrome&#038;ie=UTF-8&#038;q=creative+commons</a>). Also, if you&#8217;ve been in any sort of education system you know what plagiarism is and why it&#8217;s wrong and you shouldn&#8217;t do it. A blog, while not necessarily a revenue generator, is still someone&#8217;s work. How would you like it if I came to your house and took your car even though you worked to pay it off. It&#8217;s theft!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg</title>
		<link>http://sqlchicken.com/2010/01/the-plague-of-plagiarism/comment-page-1/#comment-1710</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Sun, 07 Nov 2010 23:22:50 +0000</pubDate>
		<guid isPermaLink="false">http://sqlchicken.com/?p=533#comment-1710</guid>
		<description>Well it is &quot;weak&quot; to copy other people&#039;s work to make personal gains, but if someone cares that much about their work they should do one of the following...

1) not post it publicly. If its valuable information that is best not shared or distributed, keep it to yourself.

2) post it in a signed or watermarked format, so it can still be accessed, still be shared, but will retain the markings of the original author. Plus in this way your work won&#039;t be modified or distorted when others share it.

3) have proper copywriting or trademarking done. Not all content posted is protected from being reused, and a lot of people probably got all protective even though they didn&#039;t even focus on their &quot;I.P.&quot; prior.</description>
		<content:encoded><![CDATA[<p>Well it is &#8220;weak&#8221; to copy other people&#8217;s work to make personal gains, but if someone cares that much about their work they should do one of the following&#8230;</p>
<p>1) not post it publicly. If its valuable information that is best not shared or distributed, keep it to yourself.</p>
<p>2) post it in a signed or watermarked format, so it can still be accessed, still be shared, but will retain the markings of the original author. Plus in this way your work won&#8217;t be modified or distorted when others share it.</p>
<p>3) have proper copywriting or trademarking done. Not all content posted is protected from being reused, and a lot of people probably got all protective even though they didn&#8217;t even focus on their &#8220;I.P.&#8221; prior.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Man, I really hope this is my last post about plagiarism. - SQL Server with Mr. Denny</title>
		<link>http://sqlchicken.com/2010/01/the-plague-of-plagiarism/comment-page-1/#comment-819</link>
		<dc:creator>Man, I really hope this is my last post about plagiarism. - SQL Server with Mr. Denny</dc:creator>
		<pubDate>Mon, 12 Apr 2010 09:01:32 +0000</pubDate>
		<guid isPermaLink="false">http://sqlchicken.com/?p=533#comment-819</guid>
		<description>[...] first time that plagiarism has reared its head recently.  The prior incidents can be found here, here, here and here (among [...]</description>
		<content:encoded><![CDATA[<p>[...] first time that plagiarism has reared its head recently.  The prior incidents can be found here, here, here and here (among [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jorge Segarra</title>
		<link>http://sqlchicken.com/2010/01/the-plague-of-plagiarism/comment-page-1/#comment-437</link>
		<dc:creator>Jorge Segarra</dc:creator>
		<pubDate>Fri, 22 Jan 2010 12:29:41 +0000</pubDate>
		<guid isPermaLink="false">http://sqlchicken.com/?p=533#comment-437</guid>
		<description>Thanks Kevin! You&#039;re right, we really haven&#039;t had a standardized &quot;OK guys, here&#039;s the deal&quot; type post. I&#039;ll get that up as soon as the craziness of SQLSaturday and publishing deadlines have passed!</description>
		<content:encoded><![CDATA[<p>Thanks Kevin! You&#8217;re right, we really haven&#8217;t had a standardized &#8220;OK guys, here&#8217;s the deal&#8221; type post. I&#8217;ll get that up as soon as the craziness of SQLSaturday and publishing deadlines have passed!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Object Caching 664/676 objects using disk: basic

Served from: sqlchicken.com @ 2012-05-17 06:58:01 -->
