MUCed Up In a Mine Field

|

I thought I would do some quick testing on my working copy of Psi to figure out what needs to be done next for MUC. I fired up the affiliation editor, and as expected I get an error message due to my query for affiliations that are 'none'. The message box is essentially empty and I was wondering why since I handle error stanzas in the Task. Looking at the XML that I received mu-conference (am I correct that this is what j.org is using?) there error stanza was tucked into an <item> element. I then checked JEP-0045 to see where the error element was supposed to appear. Turns out mu-conf isn't working correctly—again.

I have to ask, must I support these "features" or go with the JEP (which needs some work, or to be phased out in favor of MUC+)?

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

try with other MUC implementations

You also can try with other MUC implementations:
* ejabberd cvs (in 0.7.5 there was a small bug, which is fixed) should be MUC compliant
* Jive messenger also has MUC support AFAIK
* maybe Chime also has a MUC?

ps: What the f*ck is an "email address"; I just entered my JID, I hope this is ok ;-)

Ad's by Google