Ejabberd: Add support for urn:xmpp:mam:2

[marcphilipp]

What version of ejabberd are you using?

16.09

What operating system (version) are you using?

CentOS Linux release 7.2.1511

How did you install ejabberd (source, package, distribution)?

source

What did not work as expected? Are there error messages in the log? What
was the unexpected behavior? What was the expected result?

XEP-0313 (MAM) was updated earlier this year and, among other additions, uses a new namespace (urn:xmpp:mam:2). Several client libraries (e.g. Strophe.JS) already support it.

Are there any plans for ejabberd to add support for the latest version of the XEP?

[weiss]

Yes, I have such plans :-)

[marcphilipp]

Glad to hear that! 😁

Will it make it into the next release? 😇

[weiss]

Will it make it into the next release?

I just work on these things in my spare time, so I don't give any timeframes. So, unless others want to implement this, the answer is "no idea".

[marcphilipp]

Fair enough. 🙂

[omichelsen]

I did some digging, and it seems the urn:xmpp:mam:0 namespace was introduced in XEP-0313 version 0.3. It got bumped to :1 in version 0.4.1 and finally to :2 in version 0.6.

I don't see anything major/breaking in the revision history between these versions. Would it be a big issue to simply update the namespace?

We are using Strophe with a plugin setting the latest namespace. ejabberd denies this because of version mismatch, but if we manually "downgrade" the namespace in our plugin, everything works fine. It might not be an exhaustive test, but it leads me to believe that there are no breaking issues in upgrading the namespace version?

[weiss]

By announcing :2 support the server guarantees that all live messages are tagged with a stanza ID. So we can't just bump the namespace, no. We need to fix #1344, first.

[zinid]

The issue is actually resolved a few months ago, I close it.

[jovanpreet]

In which version it gets fixed??

[weiss]

In which version it gets fixed??

urn:xmpp:mam:2 is supported since ejabberd 17.11.

[jovanpreet]

Thanks

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.