<?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"
	>
<channel>
	<title>Comments on: How Far Would You Go to Protect Your Theme?</title>
	<atom:link href="http://www.freewordpressthemes.com/blog/designers/how-far-would-you-go-to-protect-your-theme/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.freewordpressthemes.com/blog/designers/how-far-would-you-go-to-protect-your-theme/</link>
	<description>Quality Free WordPress Themes</description>
	<pubDate>Wed, 23 Jul 2008 21:25:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6-bleeding2</generator>
		<item>
		<title>By: Chris Osborne</title>
		<link>http://www.freewordpressthemes.com/blog/designers/how-far-would-you-go-to-protect-your-theme/#comment-1777</link>
		<dc:creator>Chris Osborne</dc:creator>
		<pubDate>Tue, 04 Mar 2008 12:46:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.freewordpressthemes.com/blog/designers/how-far-would-you-go-to-protect-your-theme/#comment-1777</guid>
		<description>When you get the source there's not much an author can do to stop it.  However, if there is one specific place in mind where you want to get someone back there's always the revenge people have used for hotlinking.

Just have a line buried in the code somewhere that shows an image.  Make that image essentially invisible, then change it to porn when your wrath says to.

This would probably only work if you made a theme just for yourself though and didn't share.  If you put it in all copies then you would have to tell people to erase it and those instructions would leak.  And you probably wouldn't want to do this to legit paying customers at all.</description>
		<content:encoded><![CDATA[<p>When you get the source there&#8217;s not much an author can do to stop it.  However, if there is one specific place in mind where you want to get someone back there&#8217;s always the revenge people have used for hotlinking.</p>
<p>Just have a line buried in the code somewhere that shows an image.  Make that image essentially invisible, then change it to porn when your wrath says to.</p>
<p>This would probably only work if you made a theme just for yourself though and didn&#8217;t share.  If you put it in all copies then you would have to tell people to erase it and those instructions would leak.  And you probably wouldn&#8217;t want to do this to legit paying customers at all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sophia Lucero</title>
		<link>http://www.freewordpressthemes.com/blog/designers/how-far-would-you-go-to-protect-your-theme/#comment-1722</link>
		<dc:creator>Sophia Lucero</dc:creator>
		<pubDate>Thu, 28 Feb 2008 08:23:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.freewordpressthemes.com/blog/designers/how-far-would-you-go-to-protect-your-theme/#comment-1722</guid>
		<description>Until their creation becomes more specialized, it will still remain easy to steal themes. Then again, I think that's wishful thinking if you believe in the saying &lt;em&gt;if it's online, it can and will be stolen&lt;/em&gt;. And you're right, it becomes a question of how far you're willing to go to prevent that, because at the worst case scenario, you're up against the most skilled hackers in the world, and that would take a lot more knowledge than HTML/CSS/PHP coding. :)</description>
		<content:encoded><![CDATA[<p>Until their creation becomes more specialized, it will still remain easy to steal themes. Then again, I think that&#8217;s wishful thinking if you believe in the saying <em>if it&#8217;s online, it can and will be stolen</em>. And you&#8217;re right, it becomes a question of how far you&#8217;re willing to go to prevent that, because at the worst case scenario, you&#8217;re up against the most skilled hackers in the world, and that would take a lot more knowledge than HTML/CSS/PHP coding. :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
