#XMPP has specified a base set of features, beyond what's in the core protocol, for properly serving a number of different use cases in 2019; core, web, IM, mobile:
This is a good sign that the network might finally be ready to evolve beyond 1990s style #Jabber IM.
I'm not aware of anyone who sees "feature inconsistency" as a feature. The actual feature is extensibility and the cost is inconsistency.
The compliance suites are an attempt to "fix" this as much as is possible in a distributed, anarchical community.
The XSF is working on adding compliance badges so that projects can advertise their level of conformance.
Things however happen slowly because the FOSS XMPP community is small and largely made up of volunteers.
I guess that's the best possible argument for feature inconsistency but I doubt it's worth it.
IMO you can get biodiversity by having multiple independent implementations in different languages and platforms while still implementing the same spec and being largely mutually compatible and feature consistent.
@jcbrand hey, I just want to say thank u for converse. My friends use it and I'm thankful it's so great.
I'm glad you like it. By being the author I'm hyper-aware of all its flaws, so it's nice to hear that people get value out of it :D
More to come!
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!