<?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:georss="http://www.georss.org/georss" xmlns:gml="http://www.opengis.net/gml"
	>
<channel>
	<title>Comments on: WhereCamp</title>
	<atom:link href="http://highearthorbit.com/wherecamp/feed/" rel="self" type="application/rss+xml" />
	<link>http://highearthorbit.com/wherecamp/</link>
	<description>Transmitting ideas, observations, and images from 42,000 km.</description>
	<lastBuildDate>Sat, 06 Mar 2010 21:14:32 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9-rare</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andrew</title>
		<link>http://highearthorbit.com/wherecamp/comment-page-1/#comment-178321</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Wed, 21 May 2008 22:37:44 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/wherecamp/#comment-178321</guid>
		<description>@Audrey - I think FireEagle is one of the good examples paving the way of demonstrating how to handle privacy, personalization and authentication. This way users can individually decide how much &quot;innovation&quot; they&#039;re willing to play with at the cost of some privacy. They can then decide that a particular innovation may not be for them and centrally de-authorize that new service.

So developers are free to go crazy and try out new things and any user doesn&#039;t have to worry about the long-term affects of trying this service.</description>
		<content:encoded><![CDATA[<p>@Audrey &#8211; I think FireEagle is one of the good examples paving the way of demonstrating how to handle privacy, personalization and authentication. This way users can individually decide how much &#8220;innovation&#8221; they&#8217;re willing to play with at the cost of some privacy. They can then decide that a particular innovation may not be for them and centrally de-authorize that new service.</p>
<p>So developers are free to go crazy and try out new things and any user doesn&#8217;t have to worry about the long-term affects of trying this service.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Audrey</title>
		<link>http://highearthorbit.com/wherecamp/comment-page-1/#comment-178256</link>
		<dc:creator>Audrey</dc:creator>
		<pubDate>Wed, 21 May 2008 18:38:16 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/wherecamp/#comment-178256</guid>
		<description>Thanks for introducing the Six de Bono Hats idea into the geo-privacy discussion. It&#039;s frustrating when a conversation gets stuck in a gripe-loop, and I think this helped us talk about more than just fears and complaints. Maybe next time we can talk more about the how: How do we allow for privacy control and still innovate?</description>
		<content:encoded><![CDATA[<p>Thanks for introducing the Six de Bono Hats idea into the geo-privacy discussion. It&#8217;s frustrating when a conversation gets stuck in a gripe-loop, and I think this helped us talk about more than just fears and complaints. Maybe next time we can talk more about the how: How do we allow for privacy control and still innovate?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
