<?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 Infringement</title>
	<atom:link href="http://wordpresshelp.org/2009/08/03/copyright-infringement/feed/" rel="self" type="application/rss+xml" />
	<link>http://wordpresshelp.org/2009/08/03/copyright-infringement/</link>
	<description>Making WordPress Even Easier to Use!</description>
	<lastBuildDate>Wed, 12 Oct 2011 22:08:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: admin</title>
		<link>http://wordpresshelp.org/2009/08/03/copyright-infringement/comment-page-1/#comment-241</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 23 Sep 2009 01:42:48 +0000</pubDate>
		<guid isPermaLink="false">http://wordpresshelp.org/?p=127#comment-241</guid>
		<description>As it turns out, step one worked.  The folks stealing the content rolled their site back such that none of my content remains.  I found it curious that they elected to remove the content rather then ask permission to use it.  Oh well, I guess it such with those who would rather be dishonest.</description>
		<content:encoded><![CDATA[<p>As it turns out, step one worked.  The folks stealing the content rolled their site back such that none of my content remains.  I found it curious that they elected to remove the content rather then ask permission to use it.  Oh well, I guess it such with those who would rather be dishonest.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jayson</title>
		<link>http://wordpresshelp.org/2009/08/03/copyright-infringement/comment-page-1/#comment-240</link>
		<dc:creator>Jayson</dc:creator>
		<pubDate>Tue, 22 Sep 2009 23:27:04 +0000</pubDate>
		<guid isPermaLink="false">http://wordpresshelp.org/?p=127#comment-240</guid>
		<description>Totally bogus, I have been in the same boat before where another blog copied my content word for word and published it as their own.  MY very effective technique was some what like yours.  I had about 50 of my friends and colleagues post information about the piracy to every freaking social network as well as left a comment on every article on their blog &quot;calling them out&quot;.  They finally took down the information.  I would have rather just formed an appropriate alliance to share content attributing the information to the rightful owner.

Hope it works out,
Jayson</description>
		<content:encoded><![CDATA[<p>Totally bogus, I have been in the same boat before where another blog copied my content word for word and published it as their own.  MY very effective technique was some what like yours.  I had about 50 of my friends and colleagues post information about the piracy to every freaking social network as well as left a comment on every article on their blog &#8220;calling them out&#8221;.  They finally took down the information.  I would have rather just formed an appropriate alliance to share content attributing the information to the rightful owner.</p>
<p>Hope it works out,<br />
Jayson</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://wordpresshelp.org/2009/08/03/copyright-infringement/comment-page-1/#comment-208</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Mon, 03 Aug 2009 23:48:42 +0000</pubDate>
		<guid isPermaLink="false">http://wordpresshelp.org/?p=127#comment-208</guid>
		<description>You could always do a Whois search on the offending URL and forward the C&amp;D email to the registrants email, the only problem is if they provide a fake email.</description>
		<content:encoded><![CDATA[<p>You could always do a Whois search on the offending URL and forward the C&amp;D email to the registrants email, the only problem is if they provide a fake email.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

