<?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/"
		>
<channel>
	<title>Comments on: Vitality &#8211; what&#8217;s next?</title>
	<atom:link href="http://everwas.com/2007/11/vitality-whats-next.html/feed" rel="self" type="application/rss+xml" />
	<link>http://everwas.com/2007/11/vitality-whats-next.html</link>
	<description>Ian Kennedy&#039;s Blog</description>
	<lastBuildDate>Wed, 08 Feb 2012 10:31:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: ian</title>
		<link>http://everwas.com/2007/11/vitality-whats-next.html/comment-page-1#comment-1717</link>
		<dc:creator>ian</dc:creator>
		<pubDate>Fri, 23 Nov 2007 20:40:19 +0000</pubDate>
		<guid isPermaLink="false">http://everwas.com/2007/11/vitality-whats-next.html#comment-1717</guid>
		<description>Hi Niall,

I know about the existing Facebook feeds. What I&#039;m interested in is the actual content of the News Feed that&#039;s on my home page which they don&#039;t make available. As you point out, making my News Feed subscription-ready would probably backfire for Facebook because users that have their profiles buttoned up and only available to friends will need to have their updates filtered out so they don&#039;t &quot;leak&quot; into the open. There&#039;s too much room for misunderstanding and error.

I remember this particular problem with the original Bloglines.  People would add authenticated RSS feeds into their Bloglines reader and not realize that these feeds, if they were not careful, would be added to a shared database which any Bloglines subscriber could search and read.

I don&#039;t think Facebook will ever be able to open up completely just because the expectation is that what you put into Facebook is going to be viewed by those you explicitly add as a connection. The advantage goes to any service that&#039;s out on the open web aggregating social events that are already being published to the world for all to see. These services will be unencumbered by the privacy issue, they&#039;ll have more freedom to experiment and build something game-changing.</description>
		<content:encoded><![CDATA[<p>Hi Niall,</p>
<p>I know about the existing Facebook feeds. What I&#8217;m interested in is the actual content of the News Feed that&#8217;s on my home page which they don&#8217;t make available. As you point out, making my News Feed subscription-ready would probably backfire for Facebook because users that have their profiles buttoned up and only available to friends will need to have their updates filtered out so they don&#8217;t &#8220;leak&#8221; into the open. There&#8217;s too much room for misunderstanding and error.</p>
<p>I remember this particular problem with the original Bloglines.  People would add authenticated RSS feeds into their Bloglines reader and not realize that these feeds, if they were not careful, would be added to a shared database which any Bloglines subscriber could search and read.</p>
<p>I don&#8217;t think Facebook will ever be able to open up completely just because the expectation is that what you put into Facebook is going to be viewed by those you explicitly add as a connection. The advantage goes to any service that&#8217;s out on the open web aggregating social events that are already being published to the world for all to see. These services will be unencumbered by the privacy issue, they&#8217;ll have more freedom to experiment and build something game-changing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iankennedy</title>
		<link>http://everwas.com/2007/11/vitality-whats-next.html/comment-page-1#comment-3431</link>
		<dc:creator>iankennedy</dc:creator>
		<pubDate>Fri, 23 Nov 2007 20:40:00 +0000</pubDate>
		<guid isPermaLink="false">http://everwas.com/2007/11/vitality-whats-next.html#comment-3431</guid>
		<description>Hi Niall,

I know about the existing Facebook feeds. What I&#039;m interested in is the actual content of the News Feed that&#039;s on my home page which they don&#039;t make available. As you point out, making my News Feed subscription-ready would probably backfire for Facebook because users that have their profiles buttoned up and only available to friends will need to have their updates filtered out so they don&#039;t &quot;leak&quot; into the open. There&#039;s too much room for misunderstanding and error.

I remember this particular problem with the original Bloglines.  People would add authenticated RSS feeds into their Bloglines reader and not realize that these feeds, if they were not careful, would be added to a shared database which any Bloglines subscriber could search and read.

I don&#039;t think Facebook will ever be able to open up completely just because the expectation is that what you put into Facebook is going to be viewed by those you explicitly add as a connection. The advantage goes to any service that&#039;s out on the open web aggregating social events that are already being published to the world for all to see. These services will be unencumbered by the privacy issue, they&#039;ll have more freedom to experiment and build something game-changing.</description>
		<content:encoded><![CDATA[<p>Hi Niall,</p>
<p>I know about the existing Facebook feeds. What I&#8217;m interested in is the actual content of the News Feed that&#8217;s on my home page which they don&#8217;t make available. As you point out, making my News Feed subscription-ready would probably backfire for Facebook because users that have their profiles buttoned up and only available to friends will need to have their updates filtered out so they don&#8217;t &#8220;leak&#8221; into the open. There&#8217;s too much room for misunderstanding and error.</p>
<p>I remember this particular problem with the original Bloglines.  People would add authenticated RSS feeds into their Bloglines reader and not realize that these feeds, if they were not careful, would be added to a shared database which any Bloglines subscriber could search and read.</p>
<p>I don&#8217;t think Facebook will ever be able to open up completely just because the expectation is that what you put into Facebook is going to be viewed by those you explicitly add as a connection. The advantage goes to any service that&#8217;s out on the open web aggregating social events that are already being published to the world for all to see. These services will be unencumbered by the privacy issue, they&#8217;ll have more freedom to experiment and build something game-changing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Niall Kennedy</title>
		<link>http://everwas.com/2007/11/vitality-whats-next.html/comment-page-1#comment-1714</link>
		<dc:creator>Niall Kennedy</dc:creator>
		<pubDate>Fri, 23 Nov 2007 18:34:38 +0000</pubDate>
		<guid isPermaLink="false">http://everwas.com/2007/11/vitality-whats-next.html#comment-1714</guid>
		<description>&lt;a href=&quot;http://www.facebook.com/help.php?page=23&quot; rel=&quot;nofollow&quot;&gt;Facebook offers subscriptions&lt;/a&gt; for many of its features, including posted items, notifications, and status updates. Most feeds are added to web-based feed readers (My Yahoo!, Google Reader, Bloglines, etc.) and might expose private user data through each site&#039;s search function in the process. Syndicating an individual&#039;s personal data can be a bit tricky, and many companies err on the side of privacy/safety.

Adding secure communication to each feed (HTTPS) with proper per-user authentication is one way to address the issue but likely raises the support cost. We usually let users experiment with advanced features that could possibly cause injury, but in this case they might also expose the personal crushes, activities, or fears of their 200 closest &quot;friends.&quot;</description>
		<content:encoded><![CDATA[<p><a href="http://www.facebook.com/help.php?page=23" rel="nofollow">Facebook offers subscriptions</a> for many of its features, including posted items, notifications, and status updates. Most feeds are added to web-based feed readers (My Yahoo!, Google Reader, Bloglines, etc.) and might expose private user data through each site&#8217;s search function in the process. Syndicating an individual&#8217;s personal data can be a bit tricky, and many companies err on the side of privacy/safety.</p>
<p>Adding secure communication to each feed (HTTPS) with proper per-user authentication is one way to address the issue but likely raises the support cost. We usually let users experiment with advanced features that could possibly cause injury, but in this case they might also expose the personal crushes, activities, or fears of their 200 closest &#8220;friends.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Niall Kennedy</title>
		<link>http://everwas.com/2007/11/vitality-whats-next.html/comment-page-1#comment-3430</link>
		<dc:creator>Niall Kennedy</dc:creator>
		<pubDate>Fri, 23 Nov 2007 18:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://everwas.com/2007/11/vitality-whats-next.html#comment-3430</guid>
		<description>&lt;a href=&quot;http://www.facebook.com/help.php?page=23&quot; rel=&quot;nofollow&quot;&gt;Facebook offers subscriptions&lt;/a&gt; for many of its features, including posted items, notifications, and status updates. Most feeds are added to web-based feed readers (My Yahoo!, Google Reader, Bloglines, etc.) and might expose private user data through each site&#039;s search function in the process. Syndicating an individual&#039;s personal data can be a bit tricky, and many companies err on the side of privacy/safety.

Adding secure communication to each feed (HTTPS) with proper per-user authentication is one way to address the issue but likely raises the support cost. We usually let users experiment with advanced features that could possibly cause injury, but in this case they might also expose the personal crushes, activities, or fears of their 200 closest &quot;friends.&quot;</description>
		<content:encoded><![CDATA[<p><a href="http://www.facebook.com/help.php?page=23" rel="nofollow">Facebook offers subscriptions</a> for many of its features, including posted items, notifications, and status updates. Most feeds are added to web-based feed readers (My Yahoo!, Google Reader, Bloglines, etc.) and might expose private user data through each site&#8217;s search function in the process. Syndicating an individual&#8217;s personal data can be a bit tricky, and many companies err on the side of privacy/safety.</p>
<p>Adding secure communication to each feed (HTTPS) with proper per-user authentication is one way to address the issue but likely raises the support cost. We usually let users experiment with advanced features that could possibly cause injury, but in this case they might also expose the personal crushes, activities, or fears of their 200 closest &#8220;friends.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ian</title>
		<link>http://everwas.com/2007/11/vitality-whats-next.html/comment-page-1#comment-3522</link>
		<dc:creator>ian</dc:creator>
		<pubDate>Fri, 23 Nov 2007 15:40:00 +0000</pubDate>
		<guid isPermaLink="false">http://everwas.com/2007/11/vitality-whats-next.html#comment-3522</guid>
		<description>Hi Niall,&lt;br /&gt; &lt;br /&gt; I know about the existing Facebook feeds. What I&#039;m interested in is the actual content of the News Feed that&#039;s on my home page which they don&#039;t make available. As you point out, making my News Feed subscription-ready would probably backfire for Facebook because users that have their profiles buttoned up and only available to friends will need to have their updates filtered out so they don&#039;t &quot;leak&quot; into the open. There&#039;s too much room for misunderstanding and error.&lt;br /&gt; &lt;br /&gt; I remember this particular problem with the original Bloglines.  People would add authenticated RSS feeds into their Bloglines reader and not realize that these feeds, if they were not careful, would be added to a shared database which any Bloglines subscriber could search and read.&lt;br /&gt; &lt;br /&gt; I don&#039;t think Facebook will ever be able to open up completely just because the expectation is that what you put into Facebook is going to be viewed by those you explicitly add as a connection. The advantage goes to any service that&#039;s out on the open web aggregating social events that are already being published to the world for all to see. These services will be unencumbered by the privacy issue, they&#039;ll have more freedom to experiment and build something game-changing.</description>
		<content:encoded><![CDATA[<p>Hi Niall,&lt;br /&gt;<br />
 &lt;br /&gt;<br />
 I know about the existing Facebook feeds. What I&#39;m interested in is the actual content of the News Feed that&#39;s on my home page which they don&#39;t make available. As you point out, making my News Feed subscription-ready would probably backfire for Facebook because users that have their profiles buttoned up and only available to friends will need to have their updates filtered out so they don&#39;t &amp;quot;leak&amp;quot; into the open. There&#39;s too much room for misunderstanding and error.&lt;br /&gt;<br />
 &lt;br /&gt;<br />
 I remember this particular problem with the original Bloglines.  People would add authenticated RSS feeds into their Bloglines reader and not realize that these feeds, if they were not careful, would be added to a shared database which any Bloglines subscriber could search and read.&lt;br /&gt;<br />
 &lt;br /&gt;<br />
 I don&#39;t think Facebook will ever be able to open up completely just because the expectation is that what you put into Facebook is going to be viewed by those you explicitly add as a connection. The advantage goes to any service that&#39;s out on the open web aggregating social events that are already being published to the world for all to see. These services will be unencumbered by the privacy issue, they&#39;ll have more freedom to experiment and build something game-changing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Niall Kennedy</title>
		<link>http://everwas.com/2007/11/vitality-whats-next.html/comment-page-1#comment-3521</link>
		<dc:creator>Niall Kennedy</dc:creator>
		<pubDate>Fri, 23 Nov 2007 13:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://everwas.com/2007/11/vitality-whats-next.html#comment-3521</guid>
		<description>&lt;a href=&quot;http://www.facebook.com/help.php?page=23&quot; rel=&quot;nofollow&quot;&gt;Facebook offers subscriptions&lt;/a&gt; for many of its features, including posted items, notifications, and status updates. Most feeds are added to web-based feed readers (My Yahoo!, Google Reader, Bloglines, etc.) and might expose private user data through each site&#039;s search function in the process. Syndicating an individual&#039;s personal data can be a bit tricky, and many companies err on the side of privacy/safety.&lt;br /&gt; &lt;br /&gt; Adding secure communication to each feed (HTTPS) with proper per-user authentication is one way to address the issue but likely raises the support cost. We usually let users experiment with advanced features that could possibly cause injury, but in this case they might also expose the personal crushes, activities, or fears of their 200 closest &quot;friends.&quot;</description>
		<content:encoded><![CDATA[<p>&amp;lt;a href=&amp;quot;<a href="http://www.facebook.com/help.php?page=23&#038;quot" rel="nofollow">http://www.facebook.com/help.php?page=23&#038;quot</a>; rel=&amp;quot;nofollow&amp;quot;&amp;gt;Facebook offers subscriptions&amp;lt;/a&amp;gt; for many of its features, including posted items, notifications, and status updates. Most feeds are added to web-based feed readers (My Yahoo!, Google Reader, Bloglines, etc.) and might expose private user data through each site&#39;s search function in the process. Syndicating an individual&#39;s personal data can be a bit tricky, and many companies err on the side of privacy/safety.&lt;br /&gt;<br />
 &lt;br /&gt;<br />
 Adding secure communication to each feed (HTTPS) with proper per-user authentication is one way to address the issue but likely raises the support cost. We usually let users experiment with advanced features that could possibly cause injury, but in this case they might also expose the personal crushes, activities, or fears of their 200 closest &amp;quot;friends.&amp;quot;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

