<?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: I&#8217;m Sharing This!</title>
	<atom:link href="http://www.twoslashes.com/2008/06/26/im-sharing-this/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.twoslashes.com/2008/06/26/im-sharing-this/</link>
	<description>remarking on every line of life</description>
	<pubDate>Fri, 21 Nov 2008 20:53:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7-beta3-9826</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nick</title>
		<link>http://www.twoslashes.com/2008/06/26/im-sharing-this/comment-page-1/#comment-136</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Sat, 28 Jun 2008 02:14:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.twoslashes.com/?p=140#comment-136</guid>
		<description>It's not like they'd be too bothered at this point.  Even the content producers complain that the **AA's are walking away with most of the profit.</description>
		<content:encoded><![CDATA[<p>It&#8217;s not like they&#8217;d be too bothered at this point.  Even the content producers complain that the **AA&#8217;s are walking away with most of the profit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin</title>
		<link>http://www.twoslashes.com/2008/06/26/im-sharing-this/comment-page-1/#comment-135</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Sat, 28 Jun 2008 02:11:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.twoslashes.com/?p=140#comment-135</guid>
		<description>When I remember back to my law classes intent was a huge part of *most* laws of this nature. However, based on their definitions and unclear followthrough, it seems they are ignoring the intent of the user. You have a remotely hosted "share" of your important stuff as do most tech-savvy people these days. The intent here is clearly not to defraud or hurt. I think adding a line about intent would clear up the law.

The problem with this, however, is that with the current vague approach RIAA/MPAA is making money hand over fist. They send out 100 lawsuit threats and 99 of them get settled. If they had to prove intent, the number of lawsuits would be drastically reduced and thus so would their revenue stream.</description>
		<content:encoded><![CDATA[<p>When I remember back to my law classes intent was a huge part of *most* laws of this nature. However, based on their definitions and unclear followthrough, it seems they are ignoring the intent of the user. You have a remotely hosted &#8220;share&#8221; of your important stuff as do most tech-savvy people these days. The intent here is clearly not to defraud or hurt. I think adding a line about intent would clear up the law.</p>
<p>The problem with this, however, is that with the current vague approach RIAA/MPAA is making money hand over fist. They send out 100 lawsuit threats and 99 of them get settled. If they had to prove intent, the number of lawsuits would be drastically reduced and thus so would their revenue stream.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://www.twoslashes.com/2008/06/26/im-sharing-this/comment-page-1/#comment-134</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Sat, 28 Jun 2008 00:58:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.twoslashes.com/?p=140#comment-134</guid>
		<description>Well, there's nothing to prove that a properly protected share is still going to get you in trouble, so I assume you might still be safe.  But the problem is that there is no distinction made, either as far as what a "share folder" is (there are so many different ways this phrase is applied to make it any easier to enforce), or whether simply having something accessible remotely and only by yourself is going to get you in trouble.

It's the vague definitions that are giving the **AAs the edge and privilege to sue everyone and their uncle; if the courts were to give a concise but effective definition of exactly what constitutes a share with the intent to distribute, or (even better) request that the **AAs prove in each of these lawsuits that shared content &lt;em&gt;was&lt;/em&gt; indeed distributed to a third-party, and then you can start using this as a legitimate proof.</description>
		<content:encoded><![CDATA[<p>Well, there&#8217;s nothing to prove that a properly protected share is still going to get you in trouble, so I assume you might still be safe.  But the problem is that there is no distinction made, either as far as what a &#8220;share folder&#8221; is (there are so many different ways this phrase is applied to make it any easier to enforce), or whether simply having something accessible remotely and only by yourself is going to get you in trouble.</p>
<p>It&#8217;s the vague definitions that are giving the **AAs the edge and privilege to sue everyone and their uncle; if the courts were to give a concise but effective definition of exactly what constitutes a share with the intent to distribute, or (even better) request that the **AAs prove in each of these lawsuits that shared content <em>was</em> indeed distributed to a third-party, and then you can start using this as a legitimate proof.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin</title>
		<link>http://www.twoslashes.com/2008/06/26/im-sharing-this/comment-page-1/#comment-127</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Fri, 27 Jun 2008 03:26:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.twoslashes.com/?p=140#comment-127</guid>
		<description>So, by that definition, I guess Apple's "Back to My Mac" feature is setting up all .Mac/MobileMe users for failure considering their home computer is remotely accessible by another Mac, thus sharing the entire contents of the computer. I'd like to see a lawsuit on that basis. It'd clear the language up real quick.</description>
		<content:encoded><![CDATA[<p>So, by that definition, I guess Apple&#8217;s &#8220;Back to My Mac&#8221; feature is setting up all .Mac/MobileMe users for failure considering their home computer is remotely accessible by another Mac, thus sharing the entire contents of the computer. I&#8217;d like to see a lawsuit on that basis. It&#8217;d clear the language up real quick.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
