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 IM.


@Wolf480pl I wondered. Do you know if these XEPs have actually led to an increase in consistency of features, or are they just making the same requests every few years without progress? A lot of XMPP folks seem to seee feature inconsistency as a feature, not a bug :/

@strypey @Wolf480pl

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.

@jcbrand @strypey
>I'm not aware of anyone who sees "feature inconsistency" as a feature

what about biodiversity / disease resistance?

@Wolf480pl @strypey

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!

Sign in to participate in the conversation
Mastodon - NZOSS

This Mastodon instance is provided gratis by the NZ Open Source Society for the benefit of everyone interested in their own freedom and sharing with others. Hosting is generously provided by Catalyst Cloud right here in Aotearoa New Zealand.