<?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: GPL Violation</title>
	<atom:link href="http://jaidev.info/home/blog/archives/2008/02/01/gpl-violation.html/feed" rel="self" type="application/rss+xml" />
	<link>http://jaidev.info/home/blog/archives/2008/02/01/gpl-violation.html</link>
	<description></description>
	<lastBuildDate>Tue, 07 Dec 2010 08:32:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Jaidev</title>
		<link>http://jaidev.info/home/blog/archives/2008/02/01/gpl-violation.html/comment-page-1#comment-32247</link>
		<dc:creator>Jaidev</dc:creator>
		<pubDate>Sun, 03 Feb 2008 02:05:12 +0000</pubDate>
		<guid isPermaLink="false">http://jaidev.info/home/blog/archives/2008/02/01/gpl-violation.html#comment-32247</guid>
		<description>&lt;p&gt;Those two are old versions which don&#039;t work with gmail 2.0.&lt;/p&gt;
&lt;p&gt;@ravi: 
Google is quite liberal about greasemonkey, in fact, they re-wrote gmail to help GM scripts!&lt;/p&gt;
&lt;p&gt;@Jeremy:
Agree 100%. Some pleasure in calling something your own I guess!&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Those two are old versions which don&#8217;t work with gmail 2.0.</p>
<p>@ravi:<br />
Google is quite liberal about greasemonkey, in fact, they re-wrote gmail to help GM scripts!</p>
<p>@Jeremy:<br />
Agree 100%. Some pleasure in calling something your own I guess!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy</title>
		<link>http://jaidev.info/home/blog/archives/2008/02/01/gpl-violation.html/comment-page-1#comment-32232</link>
		<dc:creator>Jeremy</dc:creator>
		<pubDate>Sat, 02 Feb 2008 23:45:29 +0000</pubDate>
		<guid isPermaLink="false">http://jaidev.info/home/blog/archives/2008/02/01/gpl-violation.html#comment-32232</guid>
		<description>What strikes me as odd is why anybody would &lt;em&gt;bother&lt;/em&gt; violating the GPL? I mean, how hard is it to retain the original copyright notice?</description>
		<content:encoded><![CDATA[<p>What strikes me as odd is why anybody would <em>bother</em> violating the GPL? I mean, how hard is it to retain the original copyright notice?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ravi</title>
		<link>http://jaidev.info/home/blog/archives/2008/02/01/gpl-violation.html/comment-page-1#comment-31964</link>
		<dc:creator>ravi</dc:creator>
		<pubDate>Fri, 01 Feb 2008 07:58:12 +0000</pubDate>
		<guid isPermaLink="false">http://jaidev.info/home/blog/archives/2008/02/01/gpl-violation.html#comment-31964</guid>
		<description>I would suggest you to target at his prime motive behind plagiarism -- money from Google Adsense!

Complain to Adsense Abuse and Cc the mail to the webmaster, if you wish you can let him retain the script after duly restoring the copyright and licence notices and continue to have Google Ads on that page and if you don&#039;t want him to make money out of your scripts then make Google remove the ads from that page.

This is the most effective method of tackling such hijacks, only quirk here is that, if your script violates Google&#039;s ToC then it would be unnecessarily feeding the fire.

You could also try reporting the Web Host about this &quot;theft&quot;!</description>
		<content:encoded><![CDATA[<p>I would suggest you to target at his prime motive behind plagiarism &#8212; money from Google Adsense!</p>
<p>Complain to Adsense Abuse and Cc the mail to the webmaster, if you wish you can let him retain the script after duly restoring the copyright and licence notices and continue to have Google Ads on that page and if you don&#8217;t want him to make money out of your scripts then make Google remove the ads from that page.</p>
<p>This is the most effective method of tackling such hijacks, only quirk here is that, if your script violates Google&#8217;s ToC then it would be unnecessarily feeding the fire.</p>
<p>You could also try reporting the Web Host about this &#8220;theft&#8221;!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

