Interest in updating Openfire's MUC implementation?

[akrherz]

Howdy,

I was messing around today trying to write some MUC admin stuff from my bot client. I was pulling my hair out trying to figure out why some of my iq commands were not working based on the XEP-0045 spec. It turns out the openfire’s MUC implementation is being very long in the tooth At one point, the xmlns changed for certain activities.

MUC change user afiliation problem

Hey Emmanuel, My bad. It seems that url=http://www.jabber.org/jeps/jep-0045.htmlJEP-0045: Multi-User Chat[/url] has been modified and now adding/removing owners and admins is done using the http://jabber.org/protocol/muc#admin[/i] namespace. When we implemented MUC the http://jabber.org/protocol/muc#owner[/i] namespace was being used. We have JM-391filed to update our implementation. Feel free to vote for it to raise its priority. Meanwhile, use the old namespace to add/remove owners and admins…

OF-178

So, anybody interesting in helping to update Openfire’s MUC implementation? Maybe the devs would comment on if they would take a patch to get openfire updated to the current MUC spec?

daryl

[Mark_Walters]

Unless I’m mistaken, this is still unaddressed.

Seems like people have mentioned it since at least 2006.

Any chance Openfire will ever address this issue?

I would think updating to match spec would be pretty important.

Everyone seems to discover this issue after banging their head against the wall for a while.

And then they have to write their own workarounds.