Add support for urn:xmpp:mam:1
See original GitHub issueIn code is
Strophe.addNamespace('MAM', 'urn:xmpp:mam:2');
Openfire only accepts urn:xmpp:mam:0 and urn:xmpp:mam:1
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (12 by maintainers)
Top Results From Across the Web
XEP-0313: Message Archive Management - XMPP
An archive contains a collection of messages relevant to a particular XMPP address, e.g. a user, MUC, pubsub node, server. Note: while a...
Read more >Support for 'urn:xmpp:mam:2' in Smack?
Hi, I'm requesting the XMPP message archive with Smack 4.3.0-rc1 from our chat server using the MamManager class.
Read more >Add support for urn:xmpp:mam:2 : mam-47 - JetBrains YouTrack
Currently Tigase Message Archiving component supports MAM in version 0.5.1. Since 2017-02-17 there is a new version of MAM available with namespace ...
Read more >MUC light - MongooseIM
They have to be added by the room owner or (if configured by service administrator) ... to='coven@muclight.shakespeare.lit'> <query xmlns='urn:xmpp:mam:1' ...
Read more >service unavailable error in openfire message archive ...
openfire do not support urn:xmpp:mam:2 you have to use urn:xmpp:mam:1 instead. you have to change it in XMPPMessageArchiveManagemnt class.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
From version 4.1.3 hacking Converse to use MAM:1 instead of MAM:2 will no longer work because Converse will rely on the MAM:2 guarantee that the message archive-id is the same as the stanza-id.
This means that Converse requires archive ids to be globally unique and equivalent to the XEP-0359
stanza-id
. This is necessary for message deduplication.Also, due to this change, MAM:1 support will not be added.
Thanks. I am happy to raise a PR. Just wanted to make sure we are agreed on the purpose and intent before I start.