Follow has an “XMPP Compliance Tester”. You need to provide access to an account (I created a test account for this) and they can notify you via email of any changes.

I found it quite helpful in improving my Prosody configuration.

Keep in mind it just checks an arbitrary set of XEPs picked by the author.

They're mostly XEPs you want to support anyway.

But then there's stuff like XEP-0368: "SRV records for XMPP over TLS" which IMO should be totally optional. This one is only useful for circumventing firewalls, and only if you set it on port 443 (https). In all other cases, AFAIK it's preferable to use STARTTLS.

So to sum up: it's not as simple as making all boxes become green, w/o thinking what they do.

@Wolf480pl @rysiek

Sure, but I think it still helps.

Plus I'm not sure that STARTTLS is always preferable. I know that it once was the recommended method, and that going directly with TLS was sort of deprecated, but then people started to use DPI for STARTTLS stripping (and, iirc, STARTTLS became non-optional through a revision of the main standard as a reaction)

@xeno @rysiek
Yeah, plaintext connections are no longer allowed in XMPP.

And I do agree that the compliance tester helps, it's just that it needs to be taken with a grain of salt.

@xeno @rysiek
I'd be also good to have a compliance tester for the
"XMPP Compliance Suites ${YEAR}" things

@Wolf480pl That'd be useful, too. I honestly don't follow the development closely anymore and I'm just glad that there are tools that can tell me that XEP-12345 is now a cool thing that is supported ;-)

@Wolf480pl Anyhoo, I'm glad that there are (still) people interested in XMPP — and that the whole thing is moving forward in a direction that makes it also more useful (in terms of adapting to how things are used in this day and age).

Sign in to participate in the conversation
Mastodon is a microblogging site that federates with most instances on the Fediverse.