[Standards] Why XMPP is going on the wrong way for Pubsub commenting

Tim edhelas at gmail.com
Tue Jul 3 19:42:31 UTC 2012

I'm Jaussoin Timothée, founder of the Movim project (http://movim.eu/),
about 4 years ago we make the choice of XMPP for our project. With the
important decision to use Pubsub for the stream of our users.
Since I've read and learn a lot on XMPP and Pubsub to implement cleanly in

We also make the choice to use XEP0277 (microblogging) for our stream
implementation, with the commenting part.
Yesterday we have launched the 0.5 version of our project with the full
integration of 0277 publication+subscription+reading, also for the comments
Our XMPP server (ejabberd) have, since, big problems to support the traffic
and the request of nodes creations.
For each message posted on Movim, our plateforme create a new "comment"
node on the Pubsub server. It's dirty and fool !

I've also read the XEP0303 for this issue, and using a "comment.pubsub.com"
server to post and retrive comments is, for me, the wrong way.

Why is it so difficult to create a simple XML tree who sum up all the
informations of a post, including its comments !

  <pubsub xmlns='http://jabber.org/protocol/pubsub'>
    <publish node='urn:xmpp:microblog:0'>
      <item id='1cb57d9c-1c46-11dd-838c-001143d5d5db'>
        <entry xmlns='http://www.w3.org/2005/Atom'>
          <title type='text'>hanging out at the Caf&#233;


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20120703/2e815fee/attachment.html>

More information about the Standards mailing list