<?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/"
	
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Flickr = Censorship, Part II</title>
	<atom:link href="http://thomashawk.com/2007/06/flickr-censorship-part-ii.html/feed" rel="self" type="application/rss+xml" />
	<link>http://thomashawk.com/2007/06/flickr-censorship-part-ii.html</link>
	<description></description>
	<lastBuildDate>Sat, 26 May 2012 02:31:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Asuncion Hoggatt</title>
		<link>http://thomashawk.com/2007/06/flickr-censorship-part-ii.html/comment-page-1#comment-330946</link>
		<dc:creator>Asuncion Hoggatt</dc:creator>
		<pubDate>Sun, 14 Nov 2010 13:21:23 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/thomashawk/?p=1129#comment-330946</guid>
		<description>What a good article you wrote. Good share. But I am having trouble with this rss. I didn&#039;t succeed to subscribe. Is there anybody else experiencing similar issue with this RSS?</description>
		<content:encoded><![CDATA[<p>What a good article you wrote. Good share. But I am having trouble with this rss. I didn&#8217;t succeed to subscribe. Is there anybody else experiencing similar issue with this RSS?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: taratata</title>
		<link>http://thomashawk.com/2007/06/flickr-censorship-part-ii.html/comment-page-1#comment-7280</link>
		<dc:creator>taratata</dc:creator>
		<pubDate>Sat, 09 Jun 2007 23:53:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/thomashawk/?p=1129#comment-7280</guid>
		<description>Mr Thomas. Why don&#039;t you stop criticizing flickr and take care of your own biz, which one could call a wreck at this point.</description>
		<content:encoded><![CDATA[<p>Mr Thomas. Why don&#8217;t you stop criticizing flickr and take care of your own biz, which one could call a wreck at this point.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Swifty</title>
		<link>http://thomashawk.com/2007/06/flickr-censorship-part-ii.html/comment-page-1#comment-7281</link>
		<dc:creator>John Swifty</dc:creator>
		<pubDate>Fri, 08 Jun 2007 20:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/thomashawk/?p=1129#comment-7281</guid>
		<description>Oh my, and after saying you were going to calm down and not be so hot headed about things.&lt;br /&gt;&lt;br /&gt;This looks like things going right and things going wrong.&lt;br /&gt;&lt;br /&gt;On the right side, it seems that Violets stream &quot;tripped the automated system&#039;s prude sensors&quot;, which I&#039;m sure are there for a good reasons. Then her account got reviewed, made public again with reviewed photos marked up. A sensible review system, apparently working. It probably captures plenty that *should* be pulled from the site.&lt;br /&gt;&lt;br /&gt;On the wrong side, maybe their &quot;prude sensors&quot; are too sensitive and the feedback given to the user, Violet in this case no informative enough as to what just happened and what to expect. Bad feedback to the user.&lt;br /&gt;&lt;br /&gt;However, as I understand it from reading the forums over at Flickr, this is a fairly new system they have in place. It&#039;s fair to expect glitches with any new system, you of all people must understand that. I hardly think that in this case there are members of the Flickr team going around censoring people for the hell of it. There&#039;s just a new system with bugs in it or whatever that has yet to be fine tuned.&lt;br /&gt;&lt;br /&gt;May be &quot;Flickr = slightly over excited automated flesh detector&quot; is more along the lines.&lt;br /&gt;&lt;br /&gt;Your Zooomr system had a bug in it which exposed everyones private photos to the pubic. With the advice to &quot;just go and mark everything private again&quot;. But that was hardly &quot;Zooomr = quite the opposite of Censorship&quot;, you brushed that off as a bug, why not make a blog post about &quot;Photosharing site exposed users private photos for everyone to see&quot;?&lt;br /&gt;&lt;br /&gt;Probably because you *know* it&#039;s a bug because you&#039;re inside the system. In this case you have no idea why what happened happened, but it&#039;s probably just a good old bumps in a new system.&lt;br /&gt;&lt;br /&gt;But then that&#039;s not quite as headline grabbing is it and you just can&#039;t resist it.</description>
		<content:encoded><![CDATA[<p>Oh my, and after saying you were going to calm down and not be so hot headed about things.</p>
<p>This looks like things going right and things going wrong.</p>
<p>On the right side, it seems that Violets stream &#8220;tripped the automated system&#8217;s prude sensors&#8221;, which I&#8217;m sure are there for a good reasons. Then her account got reviewed, made public again with reviewed photos marked up. A sensible review system, apparently working. It probably captures plenty that *should* be pulled from the site.</p>
<p>On the wrong side, maybe their &#8220;prude sensors&#8221; are too sensitive and the feedback given to the user, Violet in this case no informative enough as to what just happened and what to expect. Bad feedback to the user.</p>
<p>However, as I understand it from reading the forums over at Flickr, this is a fairly new system they have in place. It&#8217;s fair to expect glitches with any new system, you of all people must understand that. I hardly think that in this case there are members of the Flickr team going around censoring people for the hell of it. There&#8217;s just a new system with bugs in it or whatever that has yet to be fine tuned.</p>
<p>May be &#8220;Flickr = slightly over excited automated flesh detector&#8221; is more along the lines.</p>
<p>Your Zooomr system had a bug in it which exposed everyones private photos to the pubic. With the advice to &#8220;just go and mark everything private again&#8221;. But that was hardly &#8220;Zooomr = quite the opposite of Censorship&#8221;, you brushed that off as a bug, why not make a blog post about &#8220;Photosharing site exposed users private photos for everyone to see&#8221;?</p>
<p>Probably because you *know* it&#8217;s a bug because you&#8217;re inside the system. In this case you have no idea why what happened happened, but it&#8217;s probably just a good old bumps in a new system.</p>
<p>But then that&#8217;s not quite as headline grabbing is it and you just can&#8217;t resist it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lane Hartwell</title>
		<link>http://thomashawk.com/2007/06/flickr-censorship-part-ii.html/comment-page-1#comment-7282</link>
		<dc:creator>Lane Hartwell</dc:creator>
		<pubDate>Fri, 08 Jun 2007 19:07:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/thomashawk/?p=1129#comment-7282</guid>
		<description>Sign me up as one of those people who is getting sick of watching out for the &quot;community&quot;, which generally means &quot;other people&#039;s kids&quot;.  Pretty much all my work is photodocumentary and yes, there are shots that show nudity and activities that some might be offended by. I have ALWAYS made those private so as not to trip the censorship wire at flickr, but I&#039;ll tell you, I don&#039;t enjoy having to do that, nor do I think it&#039;s right or fair.  I pay for my account and as a paying customer I want to show ALL of my photos - if I choose to do that.  It&#039;s your job to watch your kids, or click back if you find something offensive. Violet Blue hardly has an offensive or pornographic photostream.  I don&#039;t get it.</description>
		<content:encoded><![CDATA[<p>Sign me up as one of those people who is getting sick of watching out for the &#8220;community&#8221;, which generally means &#8220;other people&#8217;s kids&#8221;.  Pretty much all my work is photodocumentary and yes, there are shots that show nudity and activities that some might be offended by. I have ALWAYS made those private so as not to trip the censorship wire at flickr, but I&#8217;ll tell you, I don&#8217;t enjoy having to do that, nor do I think it&#8217;s right or fair.  I pay for my account and as a paying customer I want to show ALL of my photos &#8211; if I choose to do that.  It&#8217;s your job to watch your kids, or click back if you find something offensive. Violet Blue hardly has an offensive or pornographic photostream.  I don&#8217;t get it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich</title>
		<link>http://thomashawk.com/2007/06/flickr-censorship-part-ii.html/comment-page-1#comment-7283</link>
		<dc:creator>Rich</dc:creator>
		<pubDate>Fri, 08 Jun 2007 18:13:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/thomashawk/?p=1129#comment-7283</guid>
		<description>Looks like you got what you wanted.  Her account was not deleted.  Her photos were no longer blocked.  It looks like it was given thoughtful review.  &lt;br /&gt;&lt;br /&gt;&lt;i&gt;1. Any deletions should not be permanent.&lt;br /&gt;&lt;br /&gt;2. All users should have a 48 hour period to dispute conflicts when Yahoo thinks censorship is in order.&lt;br /&gt;&lt;br /&gt;3. All disputes should involve a competent, thoughtful, review.&lt;/i&gt;</description>
		<content:encoded><![CDATA[<p>Looks like you got what you wanted.  Her account was not deleted.  Her photos were no longer blocked.  It looks like it was given thoughtful review.  </p>
<p><i>1. Any deletions should not be permanent.</p>
<p>2. All users should have a 48 hour period to dispute conflicts when Yahoo thinks censorship is in order.</p>
<p>3. All disputes should involve a competent, thoughtful, review.</i></p>
]]></content:encoded>
	</item>
</channel>
</rss>

