<?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: Facebook Users Get a Big Shock With BigSight</title>
	<atom:link href="http://allancockerill.com/facebook/facebook-users-get-a-big-shock-with-bigsight/feed" rel="self" type="application/rss+xml" />
	<link>http://allancockerill.com/facebook/facebook-users-get-a-big-shock-with-bigsight</link>
	<description>Allan Cockerill writes...</description>
	<pubDate>Mon, 01 Dec 2008 18:17:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Rochelle</title>
		<link>http://allancockerill.com/facebook/facebook-users-get-a-big-shock-with-bigsight#comment-1075</link>
		<dc:creator>Rochelle</dc:creator>
		<pubDate>Mon, 28 Apr 2008 03:51:42 +0000</pubDate>
		<guid isPermaLink="false">http://allancockerill.com/facebook/facebook-users-get-a-big-shock-with-bigsight#comment-1075</guid>
		<description>Just because something is public doesn't make it public domain. Facebook doesn't own your profile image, and google doesn't appear to cache it. (Check your google cached facebook profile; the images don't go to a google db, they go back to fb.) Enabling some small element of your facebook profile for public viewing doesn't give blanket permission to start ups to snag your data, copy it, and reproduce it. What bigsight did wasn't a cache. They took the information and created a new site to represent you, without even having you agree to any TOS whatsoever.

This isn't what web 2.0 should be. And just because these guys want their site to grow doesn't mean they have a right to harvest our information, misrepresent us, and clutter up google searches.</description>
		<content:encoded><![CDATA[<p>Just because something is public doesn&#8217;t make it public domain. Facebook doesn&#8217;t own your profile image, and google doesn&#8217;t appear to cache it. (Check your google cached facebook profile; the images don&#8217;t go to a google db, they go back to fb.) Enabling some small element of your facebook profile for public viewing doesn&#8217;t give blanket permission to start ups to snag your data, copy it, and reproduce it. What bigsight did wasn&#8217;t a cache. They took the information and created a new site to represent you, without even having you agree to any TOS whatsoever.</p>
<p>This isn&#8217;t what web 2.0 should be. And just because these guys want their site to grow doesn&#8217;t mean they have a right to harvest our information, misrepresent us, and clutter up google searches.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Facebook Linkedin MySpace And Wink Privacy Issues &#124; Coffee With Allan Cockerill&#8230;</title>
		<link>http://allancockerill.com/facebook/facebook-users-get-a-big-shock-with-bigsight#comment-606</link>
		<dc:creator>Facebook Linkedin MySpace And Wink Privacy Issues &#124; Coffee With Allan Cockerill&#8230;</dc:creator>
		<pubDate>Sat, 01 Mar 2008 02:12:56 +0000</pubDate>
		<guid isPermaLink="false">http://allancockerill.com/facebook/facebook-users-get-a-big-shock-with-bigsight#comment-606</guid>
		<description>[...] Well, haven&#8217;t I opened a can of worms with my post on Facebook and Bigsight! [...]</description>
		<content:encoded><![CDATA[<p>[...] Well, haven&#8217;t I opened a can of worms with my post on Facebook and Bigsight! [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Birdwhistell</title>
		<link>http://allancockerill.com/facebook/facebook-users-get-a-big-shock-with-bigsight#comment-601</link>
		<dc:creator>Dan Birdwhistell</dc:creator>
		<pubDate>Fri, 29 Feb 2008 19:21:57 +0000</pubDate>
		<guid isPermaLink="false">http://allancockerill.com/facebook/facebook-users-get-a-big-shock-with-bigsight#comment-601</guid>
		<description>Allan,

Thanks for your post this morning, but I feel as though I need to respond given that we care deeply about these issues and I want to both clear up some errors in your post and also point out some unanswered questions.

1.  You are wrong that we in any way touched Facebook in order to obtain this basic information (name, picture, network, UID) about you.  If you look at your privacy settings on Google, you'll notice that you've enabled what is called a "public profile".  You can see it here:  http://www.facebook.com/people/Allan_Cockerill/768551039.  These public profiles are injected into the public web, appear in public search engines, and are therefore cached by myriad sites across the web.</description>
		<content:encoded><![CDATA[<p>Allan,</p>
<p>Thanks for your post this morning, but I feel as though I need to respond given that we care deeply about these issues and I want to both clear up some errors in your post and also point out some unanswered questions.</p>
<p>1.  You are wrong that we in any way touched Facebook in order to obtain this basic information (name, picture, network, UID) about you.  If you look at your privacy settings on Google, you&#8217;ll notice that you&#8217;ve enabled what is called a &#8220;public profile&#8221;.  You can see it here:  <a href="http://www.facebook.com/people/Allan_Cockerill/768551039" rel="nofollow">http://www.facebook.com/people/Allan_Cockerill/768551039</a>.  These public profiles are injected into the public web, appear in public search engines, and are therefore cached by myriad sites across the web.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
