<?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: We&#8217;re a WEF Technology Pioneer</title>
	<atom:link href="http://blog.polarrose.com/2007/11/were-a-wef-technology-pioneer/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.polarrose.com/2007/11/were-a-wef-technology-pioneer/</link>
	<description></description>
	<pubDate>Tue, 06 Jan 2009 09:47:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: T</title>
		<link>http://blog.polarrose.com/2007/11/were-a-wef-technology-pioneer/#comment-69202</link>
		<dc:creator>T</dc:creator>
		<pubDate>Tue, 04 Dec 2007 20:47:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.polarrose.com/2007/11/were-a-wef-technology-pioneer/#comment-69202</guid>
		<description>Great idea, and I'm sure you as first adopter will be enormously successful. I have three questions that I can' t find a definitive answer to anywhere else, however:

1) What is your definition of "private" photos? You have mentioned, I believe, but never confirmed that if you have to access a photo via a password, it won't be included.

2) What is your current idea of properly tagging photos to be excluded?

3) What kind of opt-out system or detagging policy are you planning to offer? Many websites recognize that private photos are easily uploaded without the photographer or subject's consent. If a copyrighted or otherwise private photo appears in the public domain, what are your current plans to deal with requests to remove this photo from your tagging? (I'm assuming a gap between getting the host to remove the photo, or a host that refuses to remove the photo despite legitimate cause). 

I've seen increasing internet chatter about these concerns, particularly #3, and thanks to Facebook's new policies these concerns are extremely topical. I'm sure you have already sought legal counsel on this issue -- you could save us all time by posting a clarified version of your policies in your privacy statement.</description>
		<content:encoded><![CDATA[<p>Great idea, and I&#8217;m sure you as first adopter will be enormously successful. I have three questions that I can&#8217; t find a definitive answer to anywhere else, however:</p>
<p>1) What is your definition of &#8220;private&#8221; photos? You have mentioned, I believe, but never confirmed that if you have to access a photo via a password, it won&#8217;t be included.</p>
<p>2) What is your current idea of properly tagging photos to be excluded?</p>
<p>3) What kind of opt-out system or detagging policy are you planning to offer? Many websites recognize that private photos are easily uploaded without the photographer or subject&#8217;s consent. If a copyrighted or otherwise private photo appears in the public domain, what are your current plans to deal with requests to remove this photo from your tagging? (I&#8217;m assuming a gap between getting the host to remove the photo, or a host that refuses to remove the photo despite legitimate cause). </p>
<p>I&#8217;ve seen increasing internet chatter about these concerns, particularly #3, and thanks to Facebook&#8217;s new policies these concerns are extremely topical. I&#8217;m sure you have already sought legal counsel on this issue&#8212;you could save us all time by posting a clarified version of your policies in your privacy statement.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://blog.polarrose.com/2007/11/were-a-wef-technology-pioneer/#comment-68659</link>
		<dc:creator>John</dc:creator>
		<pubDate>Sat, 01 Dec 2007 08:56:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.polarrose.com/2007/11/were-a-wef-technology-pioneer/#comment-68659</guid>
		<description>Polar Rose,

Well deserved. I love the plug in and look forward to seeing matching being turned on.

-- John</description>
		<content:encoded><![CDATA[<p>Polar Rose,</p>
<p>Well deserved. I love the plug in and look forward to seeing matching being turned on.<br />
&#8212;John</p>
]]></content:encoded>
	</item>
</channel>
</rss>
