A server that has mod_mam_archive loaded will return incorrect disco#info responses, confusing some clients (*cough*smack*cough*).
Example XML:
...
<feature var='urn:xmpp:archive:auto'/>
<feature xmlns='urn:xmpp:archive'>
<optional/>
</feature>
</query>
The 'urn:xmpp:archive' attribute must be of type 'var' and not a namespace, according to https://xmpp.org/extensions/xep-0136.html#disco
While technically, this is a <feature/> element qualified by some unknown namespace and shall be ignored, this is a violation of 0136 and it confuses clients that don't consider features with non-default namespaces.
A server that has mod_mam_archive loaded will return incorrect disco#info responses, confusing some clients (*cough*smack*cough*). Example XML: ... <feature var='urn:xmpp:archive:auto'/> <feature xmlns='urn:xmpp:archive'> <optional/> </feature> </query> The 'urn:xmpp:archive' attribute must be of type 'var' and not a namespace, according to https://xmpp.org/extensions/xep-0136.html#disco While technically, this is a <feature/> element qualified by some unknown namespace and shall be ignored, this is a violation of 0136 and it confuses clients that don't consider features with non-default namespaces.
This should actually not cause any problems if you use an up to date Smack version: https://github.com/igniterealtime/Smack/commit/60b07b1d679b0313550eab32e7eb48cc079533f0
I think to use the stard way of https://xmpp.org/extensions/xep-0136.html#disco is the better solution
Tagging issue as affecting a community module, not officially supported by the Prosody team.
Changes