<?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:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Bloglines, RSS privacy problem</title>
	<atom:link href="http://blogs.law.harvard.edu/palfrey/2006/08/23/bloglines-rss-privacy-problem/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/palfrey/2006/08/23/bloglines-rss-privacy-problem/</link>
	<description>From the Berkman Center at Harvard Law School</description>
	<lastBuildDate>Wed, 18 Nov 2009 13:34:17 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: phil</title>
		<link>http://blogs.law.harvard.edu/palfrey/2006/08/23/bloglines-rss-privacy-problem/comment-page-1/#comment-1946</link>
		<dc:creator>phil</dc:creator>
		<pubDate>Fri, 25 Aug 2006 19:37:50 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/palfrey/2006/08/23/bloglines-rss-privacy-problem/#comment-1946</guid>
		<description>I don&#039;t want to get into a hair-splitting contest, but this is an 80% Bloglines issue, in my opinion.  

I knew what the risk was when I gave the URL of a not-easy-to-find feed to Bloglines, but their UI is completely misleading.  If their UI had been clear enough to indicate that all feeds that I added to their system would become publicly available, then I wouldn&#039;t have added it.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t want to get into a hair-splitting contest, but this is an 80% Bloglines issue, in my opinion.  </p>
<p>I knew what the risk was when I gave the URL of a not-easy-to-find feed to Bloglines, but their UI is completely misleading.  If their UI had been clear enough to indicate that all feeds that I added to their system would become publicly available, then I wouldn&#8217;t have added it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charlie Wood</title>
		<link>http://blogs.law.harvard.edu/palfrey/2006/08/23/bloglines-rss-privacy-problem/comment-page-1/#comment-1945</link>
		<dc:creator>Charlie Wood</dc:creator>
		<pubDate>Thu, 24 Aug 2006 18:12:20 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/palfrey/2006/08/23/bloglines-rss-privacy-problem/#comment-1945</guid>
		<description>In fact this isn&#039;t a Bloglines issue, or even an RSS industry issue, but rather a Blinksale issue. There are very well-known, simple techniques for securing RSS feeds. Unfortunately Blinksale has decided not to use them and instead employs, &quot;security through obscurity,&quot; which is to say, no security at all.

In their defense, Blinksale isn&#039;t alone. Google Calendar uses the same mechanism to keep your events &quot;private&quot;, as I&#039;m sure do many others.</description>
		<content:encoded><![CDATA[<p>In fact this isn&#8217;t a Bloglines issue, or even an RSS industry issue, but rather a Blinksale issue. There are very well-known, simple techniques for securing RSS feeds. Unfortunately Blinksale has decided not to use them and instead employs, &#8220;security through obscurity,&#8221; which is to say, no security at all.</p>
<p>In their defense, Blinksale isn&#8217;t alone. Google Calendar uses the same mechanism to keep your events &#8220;private&#8221;, as I&#8217;m sure do many others.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
