<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Google Reader &#8220;shared items&#8221; provoking fury</title>
	<link>http://www.googletutor.com/2007/12/26/google-reader-shared-items-provoking-fury/</link>
	<description>Your how-to guide for Google with Google tutorials, tips for using Google and advice.</description>
	<pubDate>Mon, 13 Oct 2008 07:42:43 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Boby</title>
		<link>http://www.googletutor.com/2007/12/26/google-reader-shared-items-provoking-fury/#comment-197665</link>
		<dc:creator>Boby</dc:creator>
		<pubDate>Thu, 03 Jan 2008 21:04:37 +0000</pubDate>
		<guid>http://www.googletutor.com/2007/12/26/google-reader-shared-items-provoking-fury/#comment-197665</guid>
		<description>If you are using something free, I don't see how there can be any expectation of privacy.
I use free e-mail services, knowing that I don't own the servers, and at any time an admin could read anything I send.   You get what you pay for.</description>
		<content:encoded><![CDATA[<p>If you are using something free, I don&#8217;t see how there can be any expectation of privacy.<br />
I use free e-mail services, knowing that I don&#8217;t own the servers, and at any time an admin could read anything I send.   You get what you pay for.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://www.googletutor.com/2007/12/26/google-reader-shared-items-provoking-fury/#comment-197614</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Thu, 03 Jan 2008 15:11:57 +0000</pubDate>
		<guid>http://www.googletutor.com/2007/12/26/google-reader-shared-items-provoking-fury/#comment-197614</guid>
		<description>It seems pretty obvious to me that "shared" equals "public", but Google's response is rather audacious - "The problem isn't our software, it's that you users are using it incorrectly!"</description>
		<content:encoded><![CDATA[<p>It seems pretty obvious to me that &#8220;shared&#8221; equals &#8220;public&#8221;, but Google&#8217;s response is rather audacious - &#8220;The problem isn&#8217;t our software, it&#8217;s that you users are using it incorrectly!&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Al</title>
		<link>http://www.googletutor.com/2007/12/26/google-reader-shared-items-provoking-fury/#comment-195780</link>
		<dc:creator>Al</dc:creator>
		<pubDate>Fri, 28 Dec 2007 20:56:35 +0000</pubDate>
		<guid>http://www.googletutor.com/2007/12/26/google-reader-shared-items-provoking-fury/#comment-195780</guid>
		<description>What is wrong with this? Is there a privacy disclaimer on these shared feeds? If there were, I am not sure they would be shared. If something is considered as being private, confidential, embarrassing or proprietary why would anyone want to publish it to an internet site to begin with. Just as I have been taught about e-mail, never send anything that you would not want broadcast to the general public. This information is sent TO Google and is stored on GOOGLE OWNED SERVERS and without any disclaimers that the information will be confidential. Amazing how people carelessly mishandle information and want to blame someone else for something that, apparently, should not have been published in a public, or somewhat public forum, in the first place. 
Unfortunately, we still don't even know exactly what Google stated to this angry user because the user has published talk salad here.</description>
		<content:encoded><![CDATA[<p>What is wrong with this? Is there a privacy disclaimer on these shared feeds? If there were, I am not sure they would be shared. If something is considered as being private, confidential, embarrassing or proprietary why would anyone want to publish it to an internet site to begin with. Just as I have been taught about e-mail, never send anything that you would not want broadcast to the general public. This information is sent TO Google and is stored on GOOGLE OWNED SERVERS and without any disclaimers that the information will be confidential. Amazing how people carelessly mishandle information and want to blame someone else for something that, apparently, should not have been published in a public, or somewhat public forum, in the first place.<br />
Unfortunately, we still don&#8217;t even know exactly what Google stated to this angry user because the user has published talk salad here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ross</title>
		<link>http://www.googletutor.com/2007/12/26/google-reader-shared-items-provoking-fury/#comment-195184</link>
		<dc:creator>Ross</dc:creator>
		<pubDate>Thu, 27 Dec 2007 03:45:40 +0000</pubDate>
		<guid>http://www.googletutor.com/2007/12/26/google-reader-shared-items-provoking-fury/#comment-195184</guid>
		<description>As you have suggested, there are already two camps regarding this issue: one that was really annoyed, and another that didn't see what was the harm...

I personally don't see what's the harm. The new feature only applies to the "public" feed, which is already an indiscriminate way for sharing articles with others. I acknowledge that the "shared feed" is obfuscated, and therefore it is difficult for unauthorized users to run into it by accident, but obfuscation is no replacement for real and secure protection. Once a person emails aways the URL to his or her public feed, then that person loses control over the URL, and therefore that person is forfeiting the right to privacy. If I shared my URL with friends A, B, C, then how can I be sure that they properly protected the URL and prevented users X, Y or Z from accessing it? Even worse, if the URL is compromised, then we can't tell who leaked the URL and we can't revoke the URL. 

Because of all of that, I have always hesitated from adding any articles to my shared feed, and I didn't understand what that feature would be useful for (other than feeling free to share with the whole world).

What would have been nice of Google is to allow me to set up multiple public feeds so that I can customize the access list on a per-public-feed basis. This way, I can share my technology articles with friends at work, and political articles with friends elsewhere (just an example).</description>
		<content:encoded><![CDATA[<p>As you have suggested, there are already two camps regarding this issue: one that was really annoyed, and another that didn&#8217;t see what was the harm&#8230;</p>
<p>I personally don&#8217;t see what&#8217;s the harm. The new feature only applies to the &#8220;public&#8221; feed, which is already an indiscriminate way for sharing articles with others. I acknowledge that the &#8220;shared feed&#8221; is obfuscated, and therefore it is difficult for unauthorized users to run into it by accident, but obfuscation is no replacement for real and secure protection. Once a person emails aways the URL to his or her public feed, then that person loses control over the URL, and therefore that person is forfeiting the right to privacy. If I shared my URL with friends A, B, C, then how can I be sure that they properly protected the URL and prevented users X, Y or Z from accessing it? Even worse, if the URL is compromised, then we can&#8217;t tell who leaked the URL and we can&#8217;t revoke the URL. </p>
<p>Because of all of that, I have always hesitated from adding any articles to my shared feed, and I didn&#8217;t understand what that feature would be useful for (other than feeling free to share with the whole world).</p>
<p>What would have been nice of Google is to allow me to set up multiple public feeds so that I can customize the access list on a per-public-feed basis. This way, I can share my technology articles with friends at work, and political articles with friends elsewhere (just an example).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gavin Bollard</title>
		<link>http://www.googletutor.com/2007/12/26/google-reader-shared-items-provoking-fury/#comment-195133</link>
		<dc:creator>Gavin Bollard</dc:creator>
		<pubDate>Thu, 27 Dec 2007 01:49:24 +0000</pubDate>
		<guid>http://www.googletutor.com/2007/12/26/google-reader-shared-items-provoking-fury/#comment-195133</guid>
		<description>This is a pretty major goof on Google's part.  Obviously some people subscribed to some feeds on topics they want hidden from their other contacts.

It is a blatant disregard for privacy which could cause a lot of problems for some people. 

Examples;

If your boss can see your feed and it has employment sites on it.
If you're married and you have subscribed to personals

Google needs to lock this feature down and give their users control over their own information.  I can't see this problem dying down any other way - at the very least, it may kill Google Reader as an application.</description>
		<content:encoded><![CDATA[<p>This is a pretty major goof on Google&#8217;s part.  Obviously some people subscribed to some feeds on topics they want hidden from their other contacts.</p>
<p>It is a blatant disregard for privacy which could cause a lot of problems for some people. </p>
<p>Examples;</p>
<p>If your boss can see your feed and it has employment sites on it.<br />
If you&#8217;re married and you have subscribed to personals</p>
<p>Google needs to lock this feature down and give their users control over their own information.  I can&#8217;t see this problem dying down any other way - at the very least, it may kill Google Reader as an application.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
