Comments on: Jabber evolution http://florianjensen.com/2008/03/09/jabber-evolution/ making the world a better place! Fri, 18 Feb 2011 17:30:07 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Petteri http://florianjensen.com/2008/03/09/jabber-evolution/comment-page-1/#comment-1243 Petteri Tue, 18 Mar 2008 15:54:35 +0000 http://florianjensen.com/2008/03/09/jabber-evolution/#comment-1243 Nice to see some critical opinions on Planet jabber. Much of these blog entries are more like commercials about specific Jabber-based product. As I look at the graph it would seem that XMPP+Jabber have fever hits than Jabber before the name change. That is really sad. I think the name change and continuing support jabber name partially (jabber.org, jabber.ru etc.) just confuses people more. Compared to 2004 one thing is much better, MUC/Group chat support on Jabber clients. I hope this trend continues and we can have finally MUC rooms that can compete with IRC channels. Nice to see some critical opinions on Planet jabber. Much of these blog entries are more like commercials about specific Jabber-based product.

As I look at the graph it would seem that XMPP+Jabber have fever hits than Jabber before the name change. That is really sad. I think the name change and continuing support jabber name partially (jabber.org, jabber.ru etc.) just confuses people more.

Compared to 2004 one thing is much better, MUC/Group chat support on Jabber clients. I hope this trend continues and we can have finally MUC rooms that can compete with IRC channels.

]]> By: Arc Riley http://florianjensen.com/2008/03/09/jabber-evolution/comment-page-1/#comment-1211 Arc Riley Mon, 10 Mar 2008 00:42:55 +0000 http://florianjensen.com/2008/03/09/jabber-evolution/#comment-1211 If you're talking an XMPP-based tracker, you're not talking BitTorrent anymore, but instead a BitTorrent-like P2P system. I believe a good part of this is already in place from Jingle. Integrating a standard bittorrent client with the XMPP client, where the .torrent is downloaded via XMPP then launched using standard BitTorrent protocol, seems to be the easiest implementation. Not as elegant, but easy. If you’re talking an XMPP-based tracker, you’re not talking BitTorrent anymore, but instead a BitTorrent-like P2P system. I believe a good part of this is already in place from Jingle.

Integrating a standard bittorrent client with the XMPP client, where the .torrent is downloaded via XMPP then launched using standard BitTorrent protocol, seems to be the easiest implementation. Not as elegant, but easy.

]]> By: Florian Jensen http://florianjensen.com/2008/03/09/jabber-evolution/comment-page-1/#comment-1210 Florian Jensen Sun, 09 Mar 2008 22:42:01 +0000 http://florianjensen.com/2008/03/09/jabber-evolution/#comment-1210 I am all in favour of an XMPP-Based Tracker. And yes, the idea is to distribute the torrent file via IBB, and then launch the torrent on the client. I am all in favour of an XMPP-Based Tracker. And yes, the idea is to distribute the torrent file via IBB, and then launch the torrent on the client.

]]> By: Arc Riley http://florianjensen.com/2008/03/09/jabber-evolution/comment-page-1/#comment-1209 Arc Riley Sun, 09 Mar 2008 21:11:32 +0000 http://florianjensen.com/2008/03/09/jabber-evolution/#comment-1209 BitTorrent and XMPP is not a good match, unless you're simply sending the .torrent file over XMPP and using a standard BitTorrent tracker, and that we can already do. A more embedded solution of a XMPP-based tracker would work much slicker. It's something we're looking at for distributing game media/content with the <a href="http://www.pysoy.org/" rel="nofollow">PySoy 3d engine</a>. <a href="http://code.google.com/p/libjingle/" rel="nofollow">libjingle</a> published by Google <i>is</i> a serious mess, but what do you expect with revision 0.4? This is not Google's fault, nor is it their responsibility to release software in an implementation-ready state. We're all very thankful to them for releasing it under a free license, it's the community's role now to transform the library into something we can all use. The <a href="http://tapioca-voip.sourceforge.net/" rel="nofollow">Tapioca</a> project is one attempt to do this. BitTorrent and XMPP is not a good match, unless you’re simply sending the .torrent file over XMPP and using a standard BitTorrent tracker, and that we can already do. A more embedded solution of a XMPP-based tracker would work much slicker. It’s something we’re looking at for distributing game media/content with the PySoy 3d engine.

libjingle published by Google is a serious mess, but what do you expect with revision 0.4? This is not Google’s fault, nor is it their responsibility to release software in an implementation-ready state. We’re all very thankful to them for releasing it under a free license, it’s the community’s role now to transform the library into something we can all use. The Tapioca project is one attempt to do this.

]]> By: MattJ http://florianjensen.com/2008/03/09/jabber-evolution/comment-page-1/#comment-1208 MattJ Sun, 09 Mar 2008 20:11:22 +0000 http://florianjensen.com/2008/03/09/jabber-evolution/#comment-1208 Hmm, while I agree that there is plenty to do, I don't think the situation is that dire :) With ejabberd 2.0.0 we now have a stable server with PEP support, and built-in file transfer proxy. On the client side, Jingle is scheduled to be included in Gajim, along with e2e encryption. Psi is also catching up with new releases, etc. While all the issues you list are valid, Jabber (hmm... XMPP? :P ) is not standing still :) Hmm, while I agree that there is plenty to do, I don’t think the situation is that dire :)

With ejabberd 2.0.0 we now have a stable server with PEP support, and built-in file transfer proxy.

On the client side, Jingle is scheduled to be included in Gajim, along with e2e encryption. Psi is also catching up with new releases, etc.

While all the issues you list are valid, Jabber (hmm… XMPP? :P ) is not standing still :)

]]>