<?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: FriendFeed to XMPP Bridge &#8211; Why, how and the plan.</title>
	<atom:link href="http://briantroy.com/blog/2008/10/25/friendfeed-to-xmpp-bridge-why-how-and-the-plan/feed/" rel="self" type="application/rss+xml" />
	<link>http://briantroy.com/blog/2008/10/25/friendfeed-to-xmpp-bridge-why-how-and-the-plan/</link>
	<description>The ramblings of an often lucid mind...</description>
	<lastBuildDate>Wed, 08 Feb 2012 12:44:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: The evolution of FFStream and the Great Track Debate &#124; Brian Roy&#8217;s Blog</title>
		<link>http://briantroy.com/blog/2008/10/25/friendfeed-to-xmpp-bridge-why-how-and-the-plan/comment-page-1/#comment-264</link>
		<dc:creator>The evolution of FFStream and the Great Track Debate &#124; Brian Roy&#8217;s Blog</dc:creator>
		<pubDate>Wed, 12 Nov 2008 21:27:26 +0000</pubDate>
		<guid isPermaLink="false">http://briantroy.com/blog/2008/10/25/friendfeed-to-xmpp-bridge-why-how-and-the-plan/#comment-264</guid>
		<description>[...] those of you who follow me on twitter or friendfeed know FFStream - which I began discussing in this post - has evolved into FF-Filtered. The changes are not dramatic, but they are [...]</description>
		<content:encoded><![CDATA[<p>[...] those of you who follow me on twitter or friendfeed know FFStream &#8211; which I began discussing in this post &#8211; has evolved into FF-Filtered. The changes are not dramatic, but they are [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karoli</title>
		<link>http://briantroy.com/blog/2008/10/25/friendfeed-to-xmpp-bridge-why-how-and-the-plan/comment-page-1/#comment-595</link>
		<dc:creator>Karoli</dc:creator>
		<pubDate>Mon, 27 Oct 2008 23:48:23 +0000</pubDate>
		<guid isPermaLink="false">http://briantroy.com/blog/2008/10/25/friendfeed-to-xmpp-bridge-why-how-and-the-plan/#comment-595</guid>
		<description>Yes, that&#039;s exactly what I need.</description>
		<content:encoded><![CDATA[<p>Yes, that&#39;s exactly what I need.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: briantroy</title>
		<link>http://briantroy.com/blog/2008/10/25/friendfeed-to-xmpp-bridge-why-how-and-the-plan/comment-page-1/#comment-597</link>
		<dc:creator>briantroy</dc:creator>
		<pubDate>Mon, 27 Oct 2008 23:45:40 +0000</pubDate>
		<guid isPermaLink="false">http://briantroy.com/blog/2008/10/25/friendfeed-to-xmpp-bridge-why-how-and-the-plan/#comment-597</guid>
		<description>FFStream will implement both scope - that is FF room, list, etc - and  &lt;br&gt;keyword filter(s).&lt;br&gt;&lt;br&gt;That way if you only want limited updates for the things/subjects/ &lt;br&gt;people you really think are interesting that is what you&#039;ll get.</description>
		<content:encoded><![CDATA[<p>FFStream will implement both scope &#8211; that is FF room, list, etc &#8211; and  <br />keyword filter(s).</p>
<p>That way if you only want limited updates for the things/subjects/ <br />people you really think are interesting that is what you&#39;ll get.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: briantroy</title>
		<link>http://briantroy.com/blog/2008/10/25/friendfeed-to-xmpp-bridge-why-how-and-the-plan/comment-page-1/#comment-594</link>
		<dc:creator>briantroy</dc:creator>
		<pubDate>Mon, 27 Oct 2008 23:44:21 +0000</pubDate>
		<guid isPermaLink="false">http://briantroy.com/blog/2008/10/25/friendfeed-to-xmpp-bridge-why-how-and-the-plan/#comment-594</guid>
		<description>That will be included - you&#039;ll be able to specify a Room, A &quot;list&quot;, or  &lt;br&gt;your home feed. You can then optionally specify keywords.&lt;br&gt;Is that what you are looking for?</description>
		<content:encoded><![CDATA[<p>That will be included &#8211; you&#39;ll be able to specify a Room, A &#8220;list&#8221;, or  <br />your home feed. You can then optionally specify keywords.<br />Is that what you are looking for?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aronski</title>
		<link>http://briantroy.com/blog/2008/10/25/friendfeed-to-xmpp-bridge-why-how-and-the-plan/comment-page-1/#comment-596</link>
		<dc:creator>aronski</dc:creator>
		<pubDate>Mon, 27 Oct 2008 23:38:26 +0000</pubDate>
		<guid isPermaLink="false">http://briantroy.com/blog/2008/10/25/friendfeed-to-xmpp-bridge-why-how-and-the-plan/#comment-596</guid>
		<description>I sense that someone might have a chance to create a mobile client for this use...I&#039;m sure it will be a chore, but perhaps it will open a door for a new kind of communication. I think that especially for mobile the idea of a smaller group (controllable?) will be important. Use Friendfeeds feature to filter before it goes to XMPP.</description>
		<content:encoded><![CDATA[<p>I sense that someone might have a chance to create a mobile client for this use&#8230;I&#39;m sure it will be a chore, but perhaps it will open a door for a new kind of communication. I think that especially for mobile the idea of a smaller group (controllable?) will be important. Use Friendfeeds feature to filter before it goes to XMPP.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karoli</title>
		<link>http://briantroy.com/blog/2008/10/25/friendfeed-to-xmpp-bridge-why-how-and-the-plan/comment-page-1/#comment-593</link>
		<dc:creator>Karoli</dc:creator>
		<pubDate>Mon, 27 Oct 2008 23:32:54 +0000</pubDate>
		<guid isPermaLink="false">http://briantroy.com/blog/2008/10/25/friendfeed-to-xmpp-bridge-why-how-and-the-plan/#comment-593</guid>
		<description>Brian,&lt;br&gt;&lt;br&gt;This works great! Following aronski&#039;s suggestion above, I would suggest that there be a way to limit our xmpp feed to a specific list rather than getting the entire home feed. If someone follows 2 or 3 on FF, it&#039;s no big deal.  But for me, I need a much smaller subset of the whole feed in real time, particularly when mobile (and I use a blackberry too).&lt;br&gt;&lt;br&gt;Thanks so much for doing this!</description>
		<content:encoded><![CDATA[<p>Brian,</p>
<p>This works great! Following aronski&#39;s suggestion above, I would suggest that there be a way to limit our xmpp feed to a specific list rather than getting the entire home feed. If someone follows 2 or 3 on FF, it&#39;s no big deal.  But for me, I need a much smaller subset of the whole feed in real time, particularly when mobile (and I use a blackberry too).</p>
<p>Thanks so much for doing this!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: briantroy</title>
		<link>http://briantroy.com/blog/2008/10/25/friendfeed-to-xmpp-bridge-why-how-and-the-plan/comment-page-1/#comment-592</link>
		<dc:creator>briantroy</dc:creator>
		<pubDate>Mon, 27 Oct 2008 23:28:22 +0000</pubDate>
		<guid isPermaLink="false">http://briantroy.com/blog/2008/10/25/friendfeed-to-xmpp-bridge-why-how-and-the-plan/#comment-592</guid>
		<description>Aron - Thanks. Great points. Mobility is another key issue. XMPP  &lt;br&gt;provides a good solution for mobility - but the standard XMPP client  &lt;br&gt;isn&#039;t smart enough (IHMO) to deal with a complex set of states and  &lt;br&gt;entity relationships - as contained in the FF stream. I do however  &lt;br&gt;agree that solving for Social Media Mobility is an important issue.</description>
		<content:encoded><![CDATA[<p>Aron &#8211; Thanks. Great points. Mobility is another key issue. XMPP  <br />provides a good solution for mobility &#8211; but the standard XMPP client  <br />isn&#39;t smart enough (IHMO) to deal with a complex set of states and  <br />entity relationships &#8211; as contained in the FF stream. I do however  <br />agree that solving for Social Media Mobility is an important issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aronski</title>
		<link>http://briantroy.com/blog/2008/10/25/friendfeed-to-xmpp-bridge-why-how-and-the-plan/comment-page-1/#comment-591</link>
		<dc:creator>aronski</dc:creator>
		<pubDate>Mon, 27 Oct 2008 23:08:24 +0000</pubDate>
		<guid isPermaLink="false">http://briantroy.com/blog/2008/10/25/friendfeed-to-xmpp-bridge-why-how-and-the-plan/#comment-591</guid>
		<description>Brian, I suppose that these companies have their hands full trying to funnel data as fast as they can. Those of us who have used the Jabber/gTalk interface for Twitter and identi.ca not only for &quot;realtime&quot; updates but for track really don&#039;t want it any other way. Friendfeed to me was a good idea but I struggled with the interface. Their new beta of real time totally clicks with me. I can get it now except for the fact that in my line of work I am dependent on mobile access through my Blackberry. &lt;br&gt;&lt;br&gt;The gTalk interface not only of Twitter in the old days but Dustin&#039;s spies has been the way I can interact with my circle of friends and allow stream of keywords into my pocket during events. I am not a member of the iPhone elite, basically because of my like/dependence on IM. As usual, the manufacturers of these devices go short on memory and don&#039;t anticipate the savage use of bandwidth but hopefully they will realize they need to double up on the next rev so they can just get by when it comes out.&lt;br&gt;&lt;br&gt;I look forward to seeing how we can shape the feed from friendfeed into both a desktop and mobile experience. I suspect I will create a specific  friends list to control bandwidth for my Blackberry, but we&#039;re used to stripping down and getting just the things we want and need (and that might not lock up our devices every 30 seconds). &lt;br&gt;&lt;br&gt;I am glad that knowledgeable developers and social media fans are creating these initial workarounds because it&#039;s not only a way to get what we want from the experience of these services but to help them see where their services need to go if they care about what their users experience. Twitter has failed miserably with how it treats their users and, I guess they don&#039;t care about the small group that saw what the future is going to be, rather be a mall chat room with no attendants and nothing we want to buy.</description>
		<content:encoded><![CDATA[<p>Brian, I suppose that these companies have their hands full trying to funnel data as fast as they can. Those of us who have used the Jabber/gTalk interface for Twitter and identi.ca not only for &#8220;realtime&#8221; updates but for track really don&#39;t want it any other way. Friendfeed to me was a good idea but I struggled with the interface. Their new beta of real time totally clicks with me. I can get it now except for the fact that in my line of work I am dependent on mobile access through my Blackberry. </p>
<p>The gTalk interface not only of Twitter in the old days but Dustin&#39;s spies has been the way I can interact with my circle of friends and allow stream of keywords into my pocket during events. I am not a member of the iPhone elite, basically because of my like/dependence on IM. As usual, the manufacturers of these devices go short on memory and don&#39;t anticipate the savage use of bandwidth but hopefully they will realize they need to double up on the next rev so they can just get by when it comes out.</p>
<p>I look forward to seeing how we can shape the feed from friendfeed into both a desktop and mobile experience. I suspect I will create a specific  friends list to control bandwidth for my Blackberry, but we&#39;re used to stripping down and getting just the things we want and need (and that might not lock up our devices every 30 seconds). </p>
<p>I am glad that knowledgeable developers and social media fans are creating these initial workarounds because it&#39;s not only a way to get what we want from the experience of these services but to help them see where their services need to go if they care about what their users experience. Twitter has failed miserably with how it treats their users and, I guess they don&#39;t care about the small group that saw what the future is going to be, rather be a mall chat room with no attendants and nothing we want to buy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karoli</title>
		<link>http://briantroy.com/blog/2008/10/25/friendfeed-to-xmpp-bridge-why-how-and-the-plan/comment-page-1/#comment-399</link>
		<dc:creator>Karoli</dc:creator>
		<pubDate>Mon, 27 Oct 2008 19:48:23 +0000</pubDate>
		<guid isPermaLink="false">http://briantroy.com/blog/2008/10/25/friendfeed-to-xmpp-bridge-why-how-and-the-plan/#comment-399</guid>
		<description>Yes, that&#039;s exactly what I need.</description>
		<content:encoded><![CDATA[<p>Yes, that&#39;s exactly what I need.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: briantroy</title>
		<link>http://briantroy.com/blog/2008/10/25/friendfeed-to-xmpp-bridge-why-how-and-the-plan/comment-page-1/#comment-401</link>
		<dc:creator>briantroy</dc:creator>
		<pubDate>Mon, 27 Oct 2008 19:45:40 +0000</pubDate>
		<guid isPermaLink="false">http://briantroy.com/blog/2008/10/25/friendfeed-to-xmpp-bridge-why-how-and-the-plan/#comment-401</guid>
		<description>FFStream will implement both scope - that is FF room, list, etc - and  &lt;br&gt;keyword filter(s).&lt;br&gt;&lt;br&gt;That way if you only want limited updates for the things/subjects/ &lt;br&gt;people you really think are interesting that is what you&#039;ll get.</description>
		<content:encoded><![CDATA[<p>FFStream will implement both scope &#8211; that is FF room, list, etc &#8211; and  <br />keyword filter(s).</p>
<p>That way if you only want limited updates for the things/subjects/ <br />people you really think are interesting that is what you&#39;ll get.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
