XEP-0443: XMPP Compliance Suites 2021

[Neustradamus]

Please add support of XEP-0443: XMPP Compliance Suites 2021: https://xmpp.org/extensions/xep-0443.html

Which replaces:

• XEP-0423: XMPP Compliance Suites 2020: https://xmpp.org/extensions/xep-0423.html
• XEP-0412: XMPP Compliance Suites 2019: https://xmpp.org/extensions/xep-0412.html
• XEP-0387: XMPP Compliance Suites 2018: https://xmpp.org/extensions/xep-0387.html
• XEP-0375: XMPP Compliance Suites 2016: https://xmpp.org/extensions/xep-0375.html
• XEP-0302: XMPP Compliance Suites 2012: https://xmpp.org/extensions/xep-0302.html
• XEP-0270: XMPP Compliance Suites 2010: https://xmpp.org/extensions/xep-0270.html
• XEP-0243: XMPP Server Compliance 2009: https://xmpp.org/extensions/xep-0243.html
• XEP-0242: XMPP Client Compliance 2009: https://xmpp.org/extensions/xep-0242.html
• XEP-0216: XMPP Intermediate Server 2008: https://xmpp.org/extensions/xep-0216.html
• XEP-0212: XMPP Basic Server 2008: https://xmpp.org/extensions/xep-0212.html
• XEP-0211: XMPP Basic Client 2008: https://xmpp.org/extensions/xep-0211.html
• XEP-0073: Basic IM Protocol Suite: https://xmpp.org/extensions/xep-0073.html

[apparentlymart]

Hi @Neustradamus!

Unfortunately at this time DJabberd has no active maintainers (fellow collaborators, please correct me if I'm wrong!), and so its development is effectively frozen.

DJabberd has partial but not complete support for the functionality required by XEP-0387's definition of "Core Server" in the core compliance suite. I believe the following is a good summary of the support, but it's been a long time since I worked on this codebase so please excuse any oversights:

• The core protocol is implemented.
• TLS is implemented for c2s and s2s connections.
• XEP-0030 is implemented as a general capability but it's up to each plugin to make use of it. For example, the DJabberd::MUC component announces itself as supporting the MUC protocol.
• XEP-0114 is partially supported by DJabberd::Component::External (it supports only the "accept" variant, and not the "connect" variant.)

Significant further development is unlikely at this time, since most if not all of the maintainers have moved on to other projects and, in many cases, no longer write Perl regularly at all. 😖 If you or someone else is interested in continuing development of this codebase I expect we'd all be happy to pass the codebase on to someone who has time to invest in it, though of course I can't speak for all of the collaborators.

[Neustradamus]

Yes I know that it is unmaintained since some years...
But it is for new dev if there will be in the future...

Have you possibility to add @robn from @fastmail (@fastmailops) for merge all improvements done?

• https://github.com/fastmailops/DJabberd
• https://github.com/fastmailops/djabberd-privatestorage
• https://github.com/fastmailops/djabberd-offlinestorage

[robn]

FM (and me) are no longer running or maintaining a djabberd and I won't be able to assist in any meaningful way, but you are more than welcome to take our patches with our blessing.

[rufferson]

I've just checked XEP-0443 (CS2021) - and we have all ticks (for Advanced Core, IM and Mobile) except bookmark conversion (0411). I hoped it would go and will be replaced by 0402 (native pep) so I stopped doing 0411 till CS2021 is published.
Well and MUC of course which I didn't touch at all.

[Neustradamus]

@rufferson: There are a lot of updates since old XMPP RFCs and XEPs...

If we know what are versions of XEPs and what RFCs, it will be better to update the code...

It is for this that I have created this ticket too:

• XEPs and RFCs support page with version #38

[rufferson]

I'm not sure what do you mean by that, but if you mean old namespaces - I do track them and all xeps are supported as per their current state (or at least compatible with it - i.e. latest namespace bump).
I.e. you may see in next PR series correction for Forms XEP which was done this year.

[Neustradamus]

@rufferson: There are a lot of changes, not only namespace in XEPs...

A state of play is really important...

[rufferson]

Any breaking change must trigger bump, any non-breaking change must maintain compatibility.

Let's take MAM for example. Latest change removed some non-mandatory-to-implement features, and introduced new mandatory-to-negotiate features. My implementation was updated to support those mandatory-to-negotiate (and hence new namespace). Do I know which xep revision it is? no bloody idea. but it does support urn:xmpp:mam:2 and urn:xmpp:mam:2#extended.

In fact - extended not fully yet, no metadata and no ids hence not advertising it. But I can write in the status that I support XEP-0313 v0.7.2 (just looked at it) as I do support page flipping and before/after-id introduced by it.

Thus my point is - namespace is much more important than xep revision.