<?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: XMPP PubSub aka “death by a thousand cuts”</title>
	<atom:link href="http://code-bear.com/bearlog/2008/12/21/xmpp-pubsub-aka-%e2%80%9cdeath-by-a-thousand-cuts%e2%80%9d/feed/" rel="self" type="application/rss+xml" />
	<link>http://code-bear.com/bearlog/2008/12/21/xmpp-pubsub-aka-%e2%80%9cdeath-by-a-thousand-cuts%e2%80%9d/</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: mjc</title>
		<link>http://code-bear.com/bearlog/2008/12/21/xmpp-pubsub-aka-%e2%80%9cdeath-by-a-thousand-cuts%e2%80%9d/comment-page-1/#comment-124</link>
		<dc:creator>mjc</dc:creator>
		<pubDate>Mon, 22 Dec 2008 01:44:21 +0000</pubDate>
		<guid isPermaLink="false">http://code-bear.com/bearlog/?p=245#comment-124</guid>
		<description>totally awesome.</description>
		<content:encoded><![CDATA[<p>totally awesome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bear</title>
		<link>http://code-bear.com/bearlog/2008/12/21/xmpp-pubsub-aka-%e2%80%9cdeath-by-a-thousand-cuts%e2%80%9d/comment-page-1/#comment-126</link>
		<dc:creator>bear</dc:creator>
		<pubDate>Mon, 22 Dec 2008 00:55:51 +0000</pubDate>
		<guid isPermaLink="false">http://code-bear.com/bearlog/?p=245#comment-126</guid>
		<description>Anyone can subscribe to it by sending me an email with the JID you want to use.  We are doing the subscriptions manually just to allow me to keep track of a contact email in case something changes or I need to &quot;break&quot; the system.&lt;br&gt;&lt;br&gt;The pushing of an item to another PubSub node is called chaining and I know they (the XMPP spec folks) are working on something to cover it - but yes, technically any valid JID can be used as the target and PubSub nodes are valid JID&#039;s&lt;br&gt;&lt;br&gt;We briefly thought of using Content-Based subscriptions to allow the subscriber to control various details like format (Atom, RSS, Json) and also language (all, English, French) but quickly put that back into the &quot;future&quot; column when we discovered that it&#039;s not well implemented on either the Client or Server side :( and the last thing we want to do is bolt on a partially implemented feature to PubSub until we have more time to evaluate how.</description>
		<content:encoded><![CDATA[<p>Anyone can subscribe to it by sending me an email with the JID you want to use.  We are doing the subscriptions manually just to allow me to keep track of a contact email in case something changes or I need to &#8220;break&#8221; the system.</p>
<p>The pushing of an item to another PubSub node is called chaining and I know they (the XMPP spec folks) are working on something to cover it &#8211; but yes, technically any valid JID can be used as the target and PubSub nodes are valid JID&#39;s</p>
<p>We briefly thought of using Content-Based subscriptions to allow the subscriber to control various details like format (Atom, RSS, Json) and also language (all, English, French) but quickly put that back into the &#8220;future&#8221; column when we discovered that it&#39;s not well implemented on either the Client or Server side :( and the last thing we want to do is bolt on a partially implemented feature to PubSub until we have more time to evaluate how.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kael</title>
		<link>http://code-bear.com/bearlog/2008/12/21/xmpp-pubsub-aka-%e2%80%9cdeath-by-a-thousand-cuts%e2%80%9d/comment-page-1/#comment-125</link>
		<dc:creator>kael</dc:creator>
		<pubDate>Mon, 22 Dec 2008 00:31:25 +0000</pubDate>
		<guid isPermaLink="false">http://code-bear.com/bearlog/?p=245#comment-125</guid>
		<description>The XMPP Pubsub firehose sounds cool.&lt;br&gt;&lt;br&gt;How to subscribe it ? Would it be possible for Seesmic to publish directly to a Pubsub user node (of an &lt;i&gt;&quot;external&quot;&lt;/i&gt; server) on her behalf ?&lt;br&gt;&lt;br&gt;Also, are you aware of the &lt;a href=&quot;http://xmpp.org/extensions/xep-0060.html#impl-content&quot; rel=&quot;nofollow&quot;&gt;Content-Based Pubsub System&lt;/a&gt; which is basically a tracking system. I don&#039;t know Tigase but AFAIK there&#039;s no implementation of this capability yet. But it might interest you. :)</description>
		<content:encoded><![CDATA[<p>The XMPP Pubsub firehose sounds cool.</p>
<p>How to subscribe it ? Would it be possible for Seesmic to publish directly to a Pubsub user node (of an <i>&#8220;external&#8221;</i> server) on her behalf ?</p>
<p>Also, are you aware of the <a href="http://xmpp.org/extensions/xep-0060.html#impl-content" rel="nofollow">Content-Based Pubsub System</a> which is basically a tracking system. I don&#39;t know Tigase but AFAIK there&#39;s no implementation of this capability yet. But it might interest you. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mjc</title>
		<link>http://code-bear.com/bearlog/2008/12/21/xmpp-pubsub-aka-%e2%80%9cdeath-by-a-thousand-cuts%e2%80%9d/comment-page-1/#comment-40</link>
		<dc:creator>mjc</dc:creator>
		<pubDate>Sun, 21 Dec 2008 20:44:21 +0000</pubDate>
		<guid isPermaLink="false">http://code-bear.com/bearlog/?p=245#comment-40</guid>
		<description>totally awesome.</description>
		<content:encoded><![CDATA[<p>totally awesome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bear</title>
		<link>http://code-bear.com/bearlog/2008/12/21/xmpp-pubsub-aka-%e2%80%9cdeath-by-a-thousand-cuts%e2%80%9d/comment-page-1/#comment-39</link>
		<dc:creator>bear</dc:creator>
		<pubDate>Sun, 21 Dec 2008 19:55:51 +0000</pubDate>
		<guid isPermaLink="false">http://code-bear.com/bearlog/?p=245#comment-39</guid>
		<description>Anyone can subscribe to it by sending me an email with the JID you want to use.  We are doing the subscriptions manually just to allow me to keep track of a contact email in case something changes or I need to &quot;break&quot; the system.&lt;br&gt;&lt;br&gt;The pushing of an item to another PubSub node is called chaining and I know they (the XMPP spec folks) are working on something to cover it - but yes, technically any valid JID can be used as the target and PubSub nodes are valid JID&#039;s&lt;br&gt;&lt;br&gt;We briefly thought of using Content-Based subscriptions to allow the subscriber to control various details like format (Atom, RSS, Json) and also language (all, English, French) but quickly put that back into the &quot;future&quot; column when we discovered that it&#039;s not well implemented on either the Client or Server side :( and the last thing we want to do is bolt on a partially implemented feature to PubSub until we have more time to evaluate how.</description>
		<content:encoded><![CDATA[<p>Anyone can subscribe to it by sending me an email with the JID you want to use.  We are doing the subscriptions manually just to allow me to keep track of a contact email in case something changes or I need to &#8220;break&#8221; the system.</p>
<p>The pushing of an item to another PubSub node is called chaining and I know they (the XMPP spec folks) are working on something to cover it &#8211; but yes, technically any valid JID can be used as the target and PubSub nodes are valid JID&#39;s</p>
<p>We briefly thought of using Content-Based subscriptions to allow the subscriber to control various details like format (Atom, RSS, Json) and also language (all, English, French) but quickly put that back into the &#8220;future&#8221; column when we discovered that it&#39;s not well implemented on either the Client or Server side :( and the last thing we want to do is bolt on a partially implemented feature to PubSub until we have more time to evaluate how.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kael</title>
		<link>http://code-bear.com/bearlog/2008/12/21/xmpp-pubsub-aka-%e2%80%9cdeath-by-a-thousand-cuts%e2%80%9d/comment-page-1/#comment-38</link>
		<dc:creator>kael</dc:creator>
		<pubDate>Sun, 21 Dec 2008 19:31:25 +0000</pubDate>
		<guid isPermaLink="false">http://code-bear.com/bearlog/?p=245#comment-38</guid>
		<description>The XMPP Pubsub firehose sounds cool.&lt;br&gt;&lt;br&gt;How to subscribe it ? Would it be possible for Seesmic to publish directly to a Pubsub user node (of an &lt;i&gt;&quot;external&quot;&lt;/i&gt; server) on her behalf ?&lt;br&gt;&lt;br&gt;Also, are you aware of the &lt;a href=&quot;http://xmpp.org/extensions/xep-0060.html#impl-content&quot; rel=&quot;nofollow&quot;&gt;Content-Based Pubsub System&lt;/a&gt; which is basically a tracking system. I don&#039;t know Tigase but AFAIK there&#039;s no implementation of this capability yet. But it might interest you. :)</description>
		<content:encoded><![CDATA[<p>The XMPP Pubsub firehose sounds cool.</p>
<p>How to subscribe it ? Would it be possible for Seesmic to publish directly to a Pubsub user node (of an <i>&#8220;external&#8221;</i> server) on her behalf ?</p>
<p>Also, are you aware of the <a href="http://xmpp.org/extensions/xep-0060.html#impl-content" rel="nofollow">Content-Based Pubsub System</a> which is basically a tracking system. I don&#39;t know Tigase but AFAIK there&#39;s no implementation of this capability yet. But it might interest you. :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
