<?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: 3 Count: Burned, Man</title>
	<atom:link href="http://www.plagiarismtoday.com/2009/08/14/3-count-burned-man/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.plagiarismtoday.com/2009/08/14/3-count-burned-man/</link>
	<description>Content Theft, Plagiarism, Copyright Infringement</description>
	<lastBuildDate>Mon, 13 Feb 2012 07:59:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jonathan Bailey</title>
		<link>http://www.plagiarismtoday.com/2009/08/14/3-count-burned-man/comment-page-1/#comment-127641</link>
		<dc:creator>Jonathan Bailey</dc:creator>
		<pubDate>Mon, 17 Aug 2009 17:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.plagiarismtoday.com/?p=4364#comment-127641</guid>
		<description>Though I better understand the reasoning behind why Burning Man does what it does after reading this reply, I still have to disagree with their approach and here&#039;s why: 
 
1) The concerns they expressed in the post could be better handled through other areas of the law. Privacy issues should be handled via privacy law, If you take a photo of someone and use it for a commercial purpose, you need a model release. Without that, you have a lawsuit on your hands.  
2) It&#039;s too vague. There&#039;s no clear indication of what is permitted. This give BMO the right to change their mind at any time for any reason on these issues.  
 
The simpler solution and the more ethical one would be to ban photography altogether or ban it for certain uses (pornography, commercial, etc.) As it sits right now, if I went, I would have no idea what images I could put on my site without fear of a takedown. 
 
Right now what they are trying to do, fundamentally, is protect participant&#039;s privacy by using a sneaky rights grab in the fine print of the ticket TOS to let them use a copyright law to order removal of images. That&#039;s just a bad combination all around.  
 
I agree with what they are trying to do but strongly disagree with their approach still... </description>
		<content:encoded><![CDATA[<p>Though I better understand the reasoning behind why Burning Man does what it does after reading this reply, I still have to disagree with their approach and here&#039;s why: </p>
<p>1) The concerns they expressed in the post could be better handled through other areas of the law. Privacy issues should be handled via privacy law, If you take a photo of someone and use it for a commercial purpose, you need a model release. Without that, you have a lawsuit on your hands.<br />
2) It&#039;s too vague. There&#039;s no clear indication of what is permitted. This give BMO the right to change their mind at any time for any reason on these issues.  </p>
<p>The simpler solution and the more ethical one would be to ban photography altogether or ban it for certain uses (pornography, commercial, etc.) As it sits right now, if I went, I would have no idea what images I could put on my site without fear of a takedown. </p>
<p>Right now what they are trying to do, fundamentally, is protect participant&#039;s privacy by using a sneaky rights grab in the fine print of the ticket TOS to let them use a copyright law to order removal of images. That&#039;s just a bad combination all around.  </p>
<p>I agree with what they are trying to do but strongly disagree with their approach still&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Bailey</title>
		<link>http://www.plagiarismtoday.com/2009/08/14/3-count-burned-man/comment-page-1/#comment-132083</link>
		<dc:creator>Jonathan Bailey</dc:creator>
		<pubDate>Mon, 17 Aug 2009 17:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.plagiarismtoday.com/?p=4364#comment-132083</guid>
		<description>Though I better understand the reasoning behind why Burning Man does what it does after reading this reply, I still have to disagree with their approach and here&#039;s why:

1) The concerns they expressed in the post could be better handled through other areas of the law. Privacy issues should be handled via privacy law, If you take a photo of someone and use it for a commercial purpose, you need a model release. Without that, you have a lawsuit on your hands. 
2) It&#039;s too vague. There&#039;s no clear indication of what is permitted. This give BMO the right to change their mind at any time for any reason on these issues. 

The simpler solution and the more ethical one would be to ban photography altogether or ban it for certain uses (pornography, commercial, etc.) As it sits right now, if I went, I would have no idea what images I could put on my site without fear of a takedown.

Right now what they are trying to do, fundamentally, is protect participant&#039;s privacy by using a sneaky rights grab in the fine print of the ticket TOS to let them use a copyright law to order removal of images. That&#039;s just a bad combination all around. 

I agree with what they are trying to do but strongly disagree with their approach still...</description>
		<content:encoded><![CDATA[<p>Though I better understand the reasoning behind why Burning Man does what it does after reading this reply, I still have to disagree with their approach and here&#8217;s why:</p>
<p>1) The concerns they expressed in the post could be better handled through other areas of the law. Privacy issues should be handled via privacy law, If you take a photo of someone and use it for a commercial purpose, you need a model release. Without that, you have a lawsuit on your hands.<br />
2) It&#8217;s too vague. There&#8217;s no clear indication of what is permitted. This give BMO the right to change their mind at any time for any reason on these issues. </p>
<p>The simpler solution and the more ethical one would be to ban photography altogether or ban it for certain uses (pornography, commercial, etc.) As it sits right now, if I went, I would have no idea what images I could put on my site without fear of a takedown.</p>
<p>Right now what they are trying to do, fundamentally, is protect participant&#8217;s privacy by using a sneaky rights grab in the fine print of the ticket TOS to let them use a copyright law to order removal of images. That&#8217;s just a bad combination all around. </p>
<p>I agree with what they are trying to do but strongly disagree with their approach still&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Debora Weber-Wulff</title>
		<link>http://www.plagiarismtoday.com/2009/08/14/3-count-burned-man/comment-page-1/#comment-132082</link>
		<dc:creator>Debora Weber-Wulff</dc:creator>
		<pubDate>Sun, 16 Aug 2009 21:18:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.plagiarismtoday.com/?p=4364#comment-132082</guid>
		<description>Burning Man has published a very detailed blog entry on why they do this. It does rather make sense: &lt;a href=&quot;http://blog.burningman.com/?p=4599&quot; rel=&quot;nofollow&quot;&gt;http://blog.burningman.com/?p=4599&lt;/a&gt; </description>
		<content:encoded><![CDATA[<p>Burning Man has published a very detailed blog entry on why they do this. It does rather make sense: <a href="http://blog.burningman.com/?p=4599" rel="nofollow">http://blog.burningman.com/?p=4599</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Debora Weber-Wulff</title>
		<link>http://www.plagiarismtoday.com/2009/08/14/3-count-burned-man/comment-page-1/#comment-127624</link>
		<dc:creator>Debora Weber-Wulff</dc:creator>
		<pubDate>Sun, 16 Aug 2009 16:18:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.plagiarismtoday.com/?p=4364#comment-127624</guid>
		<description>Burning Man has published a very detailed blog entry on why they do this. It does rather make sense: &lt;a href=&quot;http://blog.burningman.com/?p=4599&quot; rel=&quot;nofollow&quot;&gt;http://blog.burningman.com/?p=4599&lt;/a&gt; </description>
		<content:encoded><![CDATA[<p>Burning Man has published a very detailed blog entry on why they do this. It does rather make sense: <a href="http://blog.burningman.com/?p=4599" rel="nofollow">http://blog.burningman.com/?p=4599</a></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

Served from: www.plagiarismtoday.com @ 2012-02-13 19:00:50 -->
