<?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: Google Wave FedOne component with Prosody XMPP server</title>
	<atom:link href="http://code-bear.com/bearlog/2009/11/01/google-wave-fedone-component-with-prosody-xmpp-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://code-bear.com/bearlog/2009/11/01/google-wave-fedone-component-with-prosody-xmpp-server/</link>
	<description>Gravity is the root of lightness; stillness, the ruler of movement</description>
	<lastBuildDate>Fri, 19 Feb 2010 10:12:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<atom:link rel="hub" href="http://pubsubhubbub.appspot.com" />
	<atom:link rel="hub" href="http://superfeedr.com/hubbub" />
		<item>
		<title>By: bear</title>
		<link>http://code-bear.com/bearlog/2009/11/01/google-wave-fedone-component-with-prosody-xmpp-server/comment-page-1/#comment-139</link>
		<dc:creator>bear</dc:creator>
		<pubDate>Mon, 02 Nov 2009 21:40:27 +0000</pubDate>
		<guid isPermaLink="false">http://code-bear.com/bearlog/2009/11/01/google-wave-fedone-component-with-prosody-xmpp-server/#comment-139</guid>
		<description>It is a complete Wave environment for sure, you can use the command line test client and view all of the Wave goodness flowing back and forth.  The only thing you don&#039;t get is the fancy UI client.&lt;br&gt;&lt;br&gt;Yep, it is completely federated - it&#039;s already making attempts to reach out and contact other servers when you add remote JID&#039;s - Google just has it turned off on the public facing servers so it fails.</description>
		<content:encoded><![CDATA[<p>It is a complete Wave environment for sure, you can use the command line test client and view all of the Wave goodness flowing back and forth.  The only thing you don&#39;t get is the fancy UI client.</p>
<p>Yep, it is completely federated &#8211; it&#39;s already making attempts to reach out and contact other servers when you add remote JID&#39;s &#8211; Google just has it turned off on the public facing servers so it fails.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reid</title>
		<link>http://code-bear.com/bearlog/2009/11/01/google-wave-fedone-component-with-prosody-xmpp-server/comment-page-1/#comment-138</link>
		<dc:creator>Reid</dc:creator>
		<pubDate>Mon, 02 Nov 2009 19:52:31 +0000</pubDate>
		<guid isPermaLink="false">http://code-bear.com/bearlog/2009/11/01/google-wave-fedone-component-with-prosody-xmpp-server/#comment-138</guid>
		<description>Hi Bear!&lt;br&gt;&lt;br&gt;Does this give you your own Wave server that you can log into and write waves in? Using the same web interface that Google has? And further, if *I* set one up, can you and I federate? Or is there some magical switch that Google needs to throw? I wouldn&#039;t think so..&lt;br&gt;&lt;br&gt;Questions, questions..</description>
		<content:encoded><![CDATA[<p>Hi Bear!</p>
<p>Does this give you your own Wave server that you can log into and write waves in? Using the same web interface that Google has? And further, if *I* set one up, can you and I federate? Or is there some magical switch that Google needs to throw? I wouldn&#39;t think so..</p>
<p>Questions, questions..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bear</title>
		<link>http://code-bear.com/bearlog/2009/11/01/google-wave-fedone-component-with-prosody-xmpp-server/comment-page-1/#comment-82</link>
		<dc:creator>bear</dc:creator>
		<pubDate>Mon, 02 Nov 2009 16:40:27 +0000</pubDate>
		<guid isPermaLink="false">http://code-bear.com/bearlog/2009/11/01/google-wave-fedone-component-with-prosody-xmpp-server/#comment-82</guid>
		<description>It is a complete Wave environment for sure, you can use the command line test client and view all of the Wave goodness flowing back and forth.  The only thing you don&#039;t get is the fancy UI client.&lt;br&gt;&lt;br&gt;Yep, it is completely federated - it&#039;s already making attempts to reach out and contact other servers when you add remote JID&#039;s - Google just has it turned off on the public facing servers so it fails.</description>
		<content:encoded><![CDATA[<p>It is a complete Wave environment for sure, you can use the command line test client and view all of the Wave goodness flowing back and forth.  The only thing you don&#39;t get is the fancy UI client.</p>
<p>Yep, it is completely federated &#8211; it&#39;s already making attempts to reach out and contact other servers when you add remote JID&#39;s &#8211; Google just has it turned off on the public facing servers so it fails.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reid</title>
		<link>http://code-bear.com/bearlog/2009/11/01/google-wave-fedone-component-with-prosody-xmpp-server/comment-page-1/#comment-81</link>
		<dc:creator>Reid</dc:creator>
		<pubDate>Mon, 02 Nov 2009 14:52:31 +0000</pubDate>
		<guid isPermaLink="false">http://code-bear.com/bearlog/2009/11/01/google-wave-fedone-component-with-prosody-xmpp-server/#comment-81</guid>
		<description>Hi Bear!&lt;br&gt;&lt;br&gt;Does this give you your own Wave server that you can log into and write waves in? Using the same web interface that Google has? And further, if *I* set one up, can you and I federate? Or is there some magical switch that Google needs to throw? I wouldn&#039;t think so..&lt;br&gt;&lt;br&gt;Questions, questions..</description>
		<content:encoded><![CDATA[<p>Hi Bear!</p>
<p>Does this give you your own Wave server that you can log into and write waves in? Using the same web interface that Google has? And further, if *I* set one up, can you and I federate? Or is there some magical switch that Google needs to throw? I wouldn&#39;t think so..</p>
<p>Questions, questions..</p>
]]></content:encoded>
	</item>
</channel>
</rss>
