TL: DR;
I’m gonna take a shot in the dark here, and guess that, for experienced XMPP client/server devs, the answer to my question is the sort of thing that one picks up by becoming familiar with the XMPP specs and extensions…
Q:
Is that an accurate assumption?
I hear you that for the vast majority of users, or users in general, this probably isn’t helpful.
In my case, I’m also a professional IT nerd — done plenty of paid (mostly corporate) work on projects, architecture design, bugs/changes/QA, planning.
Follow up:
is there a place where any of it* is being tracked or documented, either now, or in the past?
(specific issues caused by lack of using/integrating a particular XMPP extension — either in an XMPP server, or in an XMPP client).
I did find a list of extensions and clients, but it would be nice to see particular (undesired) behavior tied to particular XMPP extension's lack of support/integration.
I.e., bug reports/QA testing
Could also be expected, predictable behavior, without necessarily having to do actual testing.…
Any client that can do voice calls will work with JMP.chat. As a user generally it's not useful to think about XMPP or protocol extensions, this is an implementation detail if you're building a library or SDK. We consider Cheogram Android to be a first-party app and all Snikket branded apps to be pretty close, everything else is a third-party app with the uncertainty that entails, but basic functions like text messages and calls are standard enough to pretty much always work.