ejabberd - Comments for "How to move openfire to ejabberd?" https://www.ejabberd.im/node/1544 en Thanx a lot https://www.ejabberd.im/node/1544#comment-53347 <p>!!!</p> Fri, 27 Jun 2008 18:27:48 +0000 philipj comment 53347 at https://www.ejabberd.im Stats from public servers https://www.ejabberd.im/node/1544#comment-53345 <div class="quote-msg"> <div class="quote-author"><em>philipj</em> wrote:</div> <p>what is approx. number of concurent users "in real life" with single server ("modern" server, abt 2-4 modern CPU cores)? Is there more fresh numbers?</p></div> <p>If you want 'real life' and fresh numbers, you can check stats of Jabber servers:</p> <ul> <li><noindex><a href="http://status.jabber.org/" rel="nofollow" >jabber.org</a></noindex> </li><li><noindex><a href="http://www.jabbim.cz/about-stats.html" rel="nofollow" >jabbim.cz and other domains</a></noindex> </li><li><noindex><a href="http://re.jabber.ru/~xram/stats/" rel="nofollow" >Jabber.ru</a></noindex> </li></ul> Fri, 27 Jun 2008 17:57:56 +0000 mfoss comment 53345 at https://www.ejabberd.im About migration from Openfire to eJabberD https://www.ejabberd.im/node/1544#comment-53344 <p>Bon jour, cher Mickaël Rémond!</p> <p>AFAIK, the Openfire schema is not a secret - it can be found here (were I saw it last time :)</p> <div class="codeblock"><code>http://www.igniterealtime.org/builds/openfire/docs/latest/documentation/database-guide.html</code></div> <p>Hope it helps...</p> <p>BTW... can You please indicate, what is approx. number of concurent users "in real life" with single server ("modern" server, abt 2-4 modern CPU cores)? AFAIK, Openfire claims, that they can run abt 100k with their server... i doubt it.<br /> But for ejabberd we have just quite old benchmarks (from Erlang conference :)... Is there more fresh numbers?</p> <p>Respectueusement, Philip Jayasinghe<br /> (to not be confused, du Moscou :)</p> Fri, 27 Jun 2008 17:10:39 +0000 philipj comment 53344 at https://www.ejabberd.im XMPP PubSub and social networks monopoly https://www.ejabberd.im/node/1544#comment-51673 <div class="quote-msg"> <div class="quote-author"><em>Nick Vidal</em> wrote:</div> <p>Nice one Kael... Long time no see...<br /> I wonder where your <noindex><a href="http://del.icio.us/kael/instantsyndicating" rel="nofollow" >inspiration</a></noindex> <noindex><a href="http://wiki.jabber.org/index.php/Instant_Syndicating" rel="nofollow" >came</a></noindex> <noindex><a href="http://iss.im/" rel="nofollow" >from</a></noindex>...</p></div> <p><strong>sigh</strong></p> <p>Nick,</p> <p>Stop claiming that the idea I wrote is in any way inspired from ISS. It is so wrong.</p> <p>Apart from the expression "social networks" and PubSub, ISS and what I suggested have few things in common.</p> <p>ISS doesn't use FOAF, nor XEP-0154 neither OpenID. And I haven't waited to discover ISS to associate XMPP PubSub and social networks. So please, don't insinuate that it is a plagiarism of ISS.</p> <p>It's like claiming that cars are a plagiarism of bicycles...</p> Wed, 23 Jan 2008 22:30:07 +0000 kael comment 51673 at https://www.ejabberd.im Instant Syndicating Standards https://www.ejabberd.im/node/1544#comment-51284 <p>Nice one Kael... Long time no see...<br /> I wonder where your <noindex><a href="http://del.icio.us/kael/instantsyndicating" rel="nofollow" >inspiration</a></noindex> <noindex><a href="http://wiki.jabber.org/index.php/Instant_Syndicating" rel="nofollow" >came</a></noindex> <noindex><a href="http://iss.im/" rel="nofollow" >from</a></noindex>...</p> <p>You guys might one to check ISS (Instant Syndicating Standards). It was part of Google's Summer of Code program in 2006. The report may be found at <noindex><a href="http://wiki.jabber.org/index.php/Instant_Syndicating" rel="nofollow" >XSF's wiki</a></noindex> and the latest development may be found at <noindex><a href="http://iss.im/" rel="nofollow" >ISS' site</a></noindex>.</p> Fri, 23 Nov 2007 17:26:19 +0000 Nick Vidal comment 51284 at https://www.ejabberd.im Pubsub 1.8 was released https://www.ejabberd.im/node/1544#comment-42107 <p>Pubsub 1.8 was released 2006-06-27. ejabberd 1.1.2 was released 2006-09-27 (after three months, and it's not 1.1.3, which was released even later). Pubsub 1.8 was in a pre-release stage for a quite a long time.</p> <p>Try to create node using section 8.1.2 of XEP-0060 (note mandatory &lt;configure/&gt;). Do you really still think that ejabberd supports Pubsub?</p> <p>I claim that Pubsub version which was published a long time before 1.1.2 (not 1.1.3 even) is unsupported. Period.</p> Sun, 12 Aug 2007 16:18:11 +0000 teo comment 42107 at https://www.ejabberd.im Pubsub and PEP https://www.ejabberd.im/node/1544#comment-42105 <div class="quote-msg"> <div class="quote-author"><em>teo</em> wrote:</div> <p>Unfortunately:</p> <p>1) Pubsub itself is too general for daily use; </p></div> <p>Sorry, I disagree. We have build clients that use pubsub, with end user using pubsub daily. Yes, daily use. Pubsub has to be wrapped by the client developer to be useful. I fail to see why being general make it less useful.</p> <div class="quote-msg"> <div class="quote-author"><em>teo</em> wrote:</div> <p>2) ejabberd implements a very outdated pubsub version (even creating a node using current XEP-0060 will not work in ejabberd); </p></div> <p>When it was released ejabberd 1.1.3 implemented the latest version of pubsub. My personal opinion on this point is that XEP are evolving too fast. If you change the implementation of the XEP too often, client developers will have to change their implementation very often too and there will be a period where all clients will be not compliant. XMPP is for production these days. XMPP has left the lab a long time ago now :)</p> <p>ejabberd 2.0 will however be upgraded to support the latest Pubsub XEP.</p> <div class="quote-msg"> <div class="quote-author"><em>teo</em> wrote:</div> <p>3) reasonable simplifications like PEP (XEP-0163) isn't shipped with ejabberd (it's available as a patch, but is incomplete implementation too); </p></div> <p>PEP is good, but there is one catch. PEP is not fully compliant with Pubsub. You cannot build PEP on a standard pubsub component. You have to introduce a different behaviour. I feel it is kind of a mess.<br /> However, as stated previously, ejabberd 2.0 will be released with PEP.</p> <div class="quote-msg"> <div class="quote-author"><em>teo</em> wrote:</div> <p>4) If ejabberd will evolve so slow as during the last year, openfire will step ahead in features (it should get PEP as a Google summer of code project).</p></div> <p>We have PEP already and we are integrating it for 2.0. It is a lot of work as we are introducing at the same time a special and innovative feature in pubsub and I think and hope you will not be disapointed :)</p> <p>Openfire is a good server but has a different philosophy. ejabberd has a longer release cycle because our target is to be the most scalable, the most robust and the most flexible server. It is used as a production server for some of the largest XMPP deployment and believe me, those sites do not want to upgrade every second day, but they care about stability, scability etc.<br /> Openfire target Small Businesses, with fewer users, that need a all in one box and can afford to stop the service, upgrade more often etc. This is really different approaches.</p> <p>--<br /> Mickaël Rémond<br /> <noindex><a href="http://www.process-one.net/" rel="nofollow" >Process-one</a></noindex></p> Sun, 12 Aug 2007 13:01:11 +0000 mremond comment 42105 at https://www.ejabberd.im Unfortunately: 1) Pubsub https://www.ejabberd.im/node/1544#comment-42104 <p>Unfortunately:</p> <p>1) Pubsub itself is too general for daily use;</p> <p>2) ejabberd implements a very outdated pubsub version (even creating a node using current XEP-0060 will not work in ejabberd);</p> <p>3) reasonable simplifications like PEP (XEP-0163) isn't shipped with ejabberd (it's available as a patch, but is incomplete implementation too);</p> <p>4) If ejabberd will evolve so slow as during the last year, openfire will step ahead in features (it should get PEP as a Google summer of code project).</p> Sun, 12 Aug 2007 07:26:24 +0000 teo comment 42104 at https://www.ejabberd.im Pubsub usage https://www.ejabberd.im/node/1544#comment-42056 <p>Unfortunately, Pubsub doesn't seem very used (I have no idea what it concretely looks like) although mod_pubsub is available on lot of XMPP servers.</p> <p>I tried to create a node manually via the XML console but I didn't get it - the node seems to be there but I don't know what to do with it. :\</p> Fri, 10 Aug 2007 18:19:32 +0000 http://openid.xmpp.za.net/base64/a2FlbEBuanMubmV0bGFiLmN6 comment 42056 at https://www.ejabberd.im Social networks + FOAF + PEP + Atompub-notify-XMPP https://www.ejabberd.im/node/1544#comment-42023 <p>There have been some <noindex><a href="http://bmannconsulting.com/blog/bmann/twitter-is-jabber-part-ii" rel="nofollow" >discussions</a></noindex> about finding a way to unify the publication of presence streams.</p> <p>Although Twitter and Jaiku use XMPP for their back-end, there's no real use of Jabber (yet) ; probably because those services may prefer to use the web as the principal UI (for monetization).</p> <p>The idea would combine :</p> <p>- FOAF : users would create a FOAF file thanks to the <noindex><a href="http://www.ldodds.com/foaf/online-account" rel="nofollow" >FOAF Online Account Description Generator</a></noindex>. The file would include the RSS feed or JID related to the service.</p> <p>- User-Profile (XEP-0154) : the FOAF file would be uploaded on the Jabber server ;</p> <p>- PEP : this would then automatically create corresponding PEP nodes and their buddies could easily subscribe to their presence streams, which would additionally be displayed in status message of the publisher.</p> <p>This would require a transport that would fetch or be notified of new presence streams :</p> <p> - by ATOM-over-XMPP if the service uses atompub-notify-xmpp ;<br /> - or via a RSS transport ;<br /> - or via a Jabber-to-Jabber transport similar to the <noindex><a href="http://wiki.jrudevels.org/index.php/Eng:J2J" rel="nofollow" >J2J transport</a></noindex>.</p> <p>But this would also require an enhanced GUI, perhaps like the Coccinella message archiving one, eventually with <noindex><a href="http://www.research.ibm.com/visual/projects/history_flow/index.htm" rel="nofollow" >colors</a></noindex>. (I hope that Psi will have an additional side-pane for message archiving).</p> <p>There's also an ergonomic problem to solve with notifications (I'm using a RSS transport and have disabled events notifications, cos' I'm being flooded and it interrupts me too much).</p> <p>It doesn't solve the question of publication per se (not sure how useful it'd be to publish the same things on the different services) but it would allow to centralize presence streams.</p> <p>There might be also something to do with FOAF and OpenID thanks to the <noindex><a href="http://groups.google.com/group/foaf-dev/browse_frm/thread/d8907e955096b56a/" rel="nofollow" >foaf:openid property</a></noindex> and the XEP-0070 similarly to the <noindex><a href="http://openid.xmpp.za.net/" rel="nofollow" >OpenID authentication over XMPP system</a></noindex>.</p> <p>I haven't figured the whole picture and the idea is approximative but it might be the path to follow.</p> Fri, 10 Aug 2007 18:17:55 +0000 http://openid.xmpp.za.net/base64/a2FlbEBuanMubmV0bGFiLmN6 comment 42023 at https://www.ejabberd.im For the record, pubsub is https://www.ejabberd.im/node/1544#comment-41694 <p>For the record, pubsub is there since a looong time, officially in ejabberd. We feel we are implementing quite fast XEP, are usage tend to be lagging, I think.<br /> I am not sure a lot of deployment are using pubsub intensively (thought I am aware that some does).</p> <p>--<br /> Mickaël Rémond<br /> <noindex><a href="http://www.process-one.net/" rel="nofollow" >Process-one</a></noindex></p> Fri, 10 Aug 2007 17:06:09 +0000 mremond comment 41694 at https://www.ejabberd.im Atom+pubsub https://www.ejabberd.im/node/1544#comment-41366 <div class="quote-msg"> <div class="quote-author"><em>http://openid.xmpp.za.net/base64/a2FlbEBuanMubmV0bGFiLmN6</em> wrote:</div> <p>And for Xmas, I'd ask for an ATOM-over-XMPP component (atompub-notify-xmpp). :)</p></div> <p>This already exists, sort of. You can use <code>mod_pubsub</code> and do some extra plumbing to get interesting results. What do you have in mind?</p> Fri, 10 Aug 2007 15:42:47 +0000 legoscia comment 41366 at https://www.ejabberd.im More patches natively supported, please https://www.ejabberd.im/node/1544#comment-41282 <p>Yes, please, integrate a lot of patches for the next major release.</p> <p>There are a lot of patches but as a novice sysadmin I don't know how to patch (gotta learn); moreover patches seem to make the server more unstable with side-effects.</p> <p>Personally, I'd wish ejabberd could support PEP/PubSub, Message archiving and XEP-0154 (for FOAF) natively.</p> <p>I'm waiting for ejabberd 2.0 release to switch, though.</p> <p>And for Xmas, I'd ask for an ATOM-over-XMPP component (atompub-notify-xmpp). :)</p> <p>Cheers.</p> <p>P.S. : I have an idea of a combination of FOAF + PEP + Socialnetworks (Twitter, Jaiku, Plazes, Flickr, del.icio.us, etc) and atom-pub-notify.</p> Fri, 10 Aug 2007 14:16:25 +0000 http://openid.xmpp.za.net/base64/a2FlbEBuanMubmV0bGFiLmN6 comment 41282 at https://www.ejabberd.im XEP process https://www.ejabberd.im/node/1544#comment-41275 <div class="quote-msg"> <div class="quote-author"><em>http://openid.xmpp.za.net/base64/a2FlbEBuanMubmV0bGFiLmN6</em> wrote:</div> <p>Regarding the Asterisk-IM plugin, there's a <noindex><a href="http://www.igniterealtime.org/fisheye/viewrep/~raw,r=2878/svn-org/asterisk-im/trunk/documentation/phone_jep.html" rel="nofollow" >Phone Integration Proto-JEP</a></noindex>.</p></div> <p>I know, as I have said the problem is they need seems to be interested to move this to the <noindex><a href="http://www.xmpp.org/extensions/xep-0001.html" rel="nofollow" >XEP process</a></noindex>. As long as they do not push protocol extensions they make to the XEP process so that other Jabber projects will/can use them, Jive Software is not contributing that much to the Jabber community (this is more worth that sponsoring the XSF!).</p> <p>--<br /> sander</p> Fri, 10 Aug 2007 09:35:33 +0000 sander comment 41275 at https://www.ejabberd.im PEP has been available for a https://www.ejabberd.im/node/1544#comment-41271 <p>PEP has been available for a long time as a patch.<br /> We are integrated it in ejabberd 2.0, but we are adapting it to a new pubsub implementation which is much better that the current one. I should write a blog post to describe it :)</p> <p>--<br /> Mickaël Rémond<br /> <noindex><a href="http://www.process-one.net/" rel="nofollow" >Process-one</a></noindex></p> Fri, 10 Aug 2007 06:46:47 +0000 mremond comment 41271 at https://www.ejabberd.im