<?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"
	>
<channel>
	<title>Comments for defuze.org</title>
	<atom:link href="http://www.defuze.org/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://www.defuze.org</link>
	<description></description>
	<pubDate>Wed, 10 Mar 2010 17:47:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>Comment on headstock: XMPP library based on Kamaelia by Sylvain Hellegouarch</title>
		<link>http://www.defuze.org/archives/44-headstock-xmpp-library-based-on-kamaelia.html#comment-734</link>
		<dc:creator>Sylvain Hellegouarch</dc:creator>
		<pubDate>Mon, 25 Jan 2010 13:30:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.defuze.org/archives/15-guid.html#comment-734</guid>
		<description>Hi Dan,

Let's put aside the language in which the code would be written into for now. Using XMPP with smartphones can be like the greatest idea since the butter knife or a very painful one. Basically the iphone will suck at XMPP. Not from a framework point of view but because you can't have a daemon process that stays up. Android offers that and there XMPP is just too much fun (notably because the connected socket doesn't actually consume much energy).

Now for the purpose you're suggesting, if you're going to perform discrete tasks in a single direction (from the remote to the TV). Why even using XMPP? HTTP would seem just as good.</description>
		<content:encoded><![CDATA[<p>Hi Dan,</p>
<p>Let&#8217;s put aside the language in which the code would be written into for now. Using XMPP with smartphones can be like the greatest idea since the butter knife or a very painful one. Basically the iphone will suck at XMPP. Not from a framework point of view but because you can&#8217;t have a daemon process that stays up. Android offers that and there XMPP is just too much fun (notably because the connected socket doesn&#8217;t actually consume much energy).</p>
<p>Now for the purpose you&#8217;re suggesting, if you&#8217;re going to perform discrete tasks in a single direction (from the remote to the TV). Why even using XMPP? HTTP would seem just as good.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on headstock: XMPP library based on Kamaelia by Dan Brickley</title>
		<link>http://www.defuze.org/archives/44-headstock-xmpp-library-based-on-kamaelia.html#comment-733</link>
		<dc:creator>Dan Brickley</dc:creator>
		<pubDate>Mon, 25 Jan 2010 11:21:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.defuze.org/archives/15-guid.html#comment-733</guid>
		<description>Hi  Sylvain! 

I've been looking around the various Python XMPP libraries trying to pick the one most likely to support local-link communications - a mix of XEP-0174 (which also has a bunch of dns discovery magic), and the various Jingle pieces. Do you have any plans in that direction? 

Context - I'm looking at this for smartphone remote controls - http://mail.jabber.org/pipermail/social/2009-August/000547.html etc - and so cutting out network latency is quite attractive of course. 

I don't mind using public XMPP network as a one time cost, eg. for discovery and authentication... so long as most comms can later happen locally. Ideally I'm looking for a Py library that could eg be bundled inside a Boxee/XBMC plugin, but that might be a bit ambitious :) Without the link-local approach, I'm left playing tricks like using iphone motion sensors to reactivate the XMPP connection when the remote is about to be used...

Thanks for any thoughts on whether headstrong would be a good fit!</description>
		<content:encoded><![CDATA[<p>Hi  Sylvain! </p>
<p>I&#8217;ve been looking around the various Python XMPP libraries trying to pick the one most likely to support local-link communications - a mix of XEP-0174 (which also has a bunch of dns discovery magic), and the various Jingle pieces. Do you have any plans in that direction? </p>
<p>Context - I&#8217;m looking at this for smartphone remote controls - <a href="http://mail.jabber.org/pipermail/social/2009-August/000547.html" rel="nofollow">http://mail.jabber.org/pipermail/social/2009-August/000547.html</a> etc - and so cutting out network latency is quite attractive of course. </p>
<p>I don&#8217;t mind using public XMPP network as a one time cost, eg. for discovery and authentication&#8230; so long as most comms can later happen locally. Ideally I&#8217;m looking for a Py library that could eg be bundled inside a Boxee/XBMC plugin, but that might be a bit ambitious <img src='http://www.defuze.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> Without the link-local approach, I&#8217;m left playing tricks like using iphone motion sensors to reactivate the XMPP connection when the remote is about to be used&#8230;</p>
<p>Thanks for any thoughts on whether headstrong would be a good fit!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Beyond superfeedr awesomeness by Julien</title>
		<link>http://www.defuze.org/archives/195-beyond-superfeedr-awesomeness.html#comment-703</link>
		<dc:creator>Julien</dc:creator>
		<pubDate>Wed, 09 Dec 2009 23:28:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.defuze.org/?p=195#comment-703</guid>
		<description>hey, it's a ton of great ideas, for sure. However, I kind of disagree with you when you say it's superfeedr's job to implemet job. Our approach is just to provide the pipes... you build the coolness on top of it.

This is the great stuff with XMPP PubSub our pubSubHubbub : they're just design patterns in a way and they can applu to all the stuff above, as long as you build the feeds and the logic on top!</description>
		<content:encoded><![CDATA[<p>hey, it&#8217;s a ton of great ideas, for sure. However, I kind of disagree with you when you say it&#8217;s superfeedr&#8217;s job to implemet job. Our approach is just to provide the pipes&#8230; you build the coolness on top of it.</p>
<p>This is the great stuff with XMPP PubSub our pubSubHubbub : they&#8217;re just design patterns in a way and they can applu to all the stuff above, as long as you build the feeds and the logic on top!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Atom and AtomPub were failed by Julien</title>
		<link>http://www.defuze.org/archives/171-atom-and-atompub-were-failed.html#comment-668</link>
		<dc:creator>Julien</dc:creator>
		<pubDate>Sun, 19 Apr 2009 16:36:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.defuze.org/?p=171#comment-668</guid>
		<description>I can't agree more... but on the other end, I think Web Hooks (if they ever become big) will give AtomPub a nice occasion to grow beyond what it is right now.

XMPP is 10 yrs old, and, despite the fact that it's "trendier" as ever, it's not widespread. Let's give AtomPub a few more years!</description>
		<content:encoded><![CDATA[<p>I can&#8217;t agree more&#8230; but on the other end, I think Web Hooks (if they ever become big) will give AtomPub a nice occasion to grow beyond what it is right now.</p>
<p>XMPP is 10 yrs old, and, despite the fact that it&#8217;s &#8220;trendier&#8221; as ever, it&#8217;s not widespread. Let&#8217;s give AtomPub a few more years!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Is XMPP for the web ready? by Jason</title>
		<link>http://www.defuze.org/archives/163-is-xmpp-for-the-web-ready.html#comment-665</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Thu, 16 Apr 2009 02:12:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.defuze.org/?p=163#comment-665</guid>
		<description>This is the nearest thing I've found. The code is available as links to patches on this page, but nowhere could I find it on the jabsorb site or svn. http://groups.google.com/group/jabsorb-user/browse_thread/thread/47a8753888be73d5</description>
		<content:encoded><![CDATA[<p>This is the nearest thing I&#8217;ve found. The code is available as links to patches on this page, but nowhere could I find it on the jabsorb site or svn. <a href="http://groups.google.com/group/jabsorb-user/browse_thread/thread/47a8753888be73d5" rel="nofollow">http://groups.google.com/group/jabsorb-user/browse_thread/thread/47a8753888be73d5</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Geolocalization and microblogging by adrian</title>
		<link>http://www.defuze.org/archives/137-geolocalization-and-microblogging.html#comment-664</link>
		<dc:creator>adrian</dc:creator>
		<pubDate>Wed, 15 Apr 2009 08:23:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.defuze.org/?p=137#comment-664</guid>
		<description>Nice :)</description>
		<content:encoded><![CDATA[<p>Nice <img src='http://www.defuze.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Is XMPP for the web ready? by Howard</title>
		<link>http://www.defuze.org/archives/163-is-xmpp-for-the-web-ready.html#comment-641</link>
		<dc:creator>Howard</dc:creator>
		<pubDate>Sat, 07 Mar 2009 06:56:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.defuze.org/?p=163#comment-641</guid>
		<description>Normally I would agree that integrating a new protocol in the browser is hard. However, I tried this open source project  (kaazing.org) awhile back and it seemed like a very compelling solution, but I never got a chance to finish the testing. They claim that they have solved the issue of running a native XMPP client in the browser. Would be great to hear if someone else have tried it out.</description>
		<content:encoded><![CDATA[<p>Normally I would agree that integrating a new protocol in the browser is hard. However, I tried this open source project  (kaazing.org) awhile back and it seemed like a very compelling solution, but I never got a chance to finish the testing. They claim that they have solved the issue of running a native XMPP client in the browser. Would be great to hear if someone else have tried it out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Notifixious - A notification platform by Jason Salas</title>
		<link>http://www.defuze.org/archives/57-notifixious-a-notification-platform.html#comment-638</link>
		<dc:creator>Jason Salas</dc:creator>
		<pubDate>Thu, 05 Mar 2009 01:01:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.defuze.org/archives/28-guid.html#comment-638</guid>
		<description>I did a '7 Questions' post with Notifixious here: http://jasonsalas.com/2009/02/7-questions-for-notifixious.html</description>
		<content:encoded><![CDATA[<p>I did a &#8216;7 Questions&#8217; post with Notifixious here: <a href="http://jasonsalas.com/2009/02/7-questions-for-notifixious.html" rel="nofollow">http://jasonsalas.com/2009/02/7-questions-for-notifixious.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ubikod: Here I come by Sylvain Hellegouarch</title>
		<link>http://www.defuze.org/archives/169-ubikod-here-i-come.html#comment-637</link>
		<dc:creator>Sylvain Hellegouarch</dc:creator>
		<pubDate>Wed, 04 Mar 2009 09:05:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.defuze.org/?p=169#comment-637</guid>
		<description>@M. David: Full time gig yeah :)

@Laurent: as I am ;)</description>
		<content:encoded><![CDATA[<p>@M. David: Full time gig yeah <img src='http://www.defuze.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>@Laurent: as I am <img src='http://www.defuze.org/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ubikod: Here I come by laurent</title>
		<link>http://www.defuze.org/archives/169-ubikod-here-i-come.html#comment-636</link>
		<dc:creator>laurent</dc:creator>
		<pubDate>Tue, 03 Mar 2009 21:15:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.defuze.org/?p=169#comment-636</guid>
		<description>I must say we are pretty excited to have you on board, Sylvain !</description>
		<content:encoded><![CDATA[<p>I must say we are pretty excited to have you on board, Sylvain !</p>
]]></content:encoded>
	</item>
</channel>
</rss>
