Oh boy, these two are starting to look really similar!

spec.matrix.org/latest/

xmpp.org/extensions/xep-0001.h

One of the early, often repeated arguments in favor of #matrix over #xmpp was that it didn't have complicated standards and extensions that one had to keep track of.

I'm curious to know what the difference between the systems is in terms of procedures, governance etc. are? What lessons have been drawn from two decades of XEPs? (Or three-and-a-half decades of IETF)

How does one make sure the system still works after, let's say a decade, when it is no longer exciting and new and everyone is full of energy? When it has become yet another grueling technical bureaucracy like any other real world (open?) standard which needs to deal with legacies, weird real-world requirements and parties which have really different opinions? Not even touching upon corporate capture here.

The same goes for #fediverse and the talk about #FEP or fediverse enhancement proposals.

This is not meant to disparage these processes at all, by the way. Rather, these are genuine questions on how to make this work because we need this kind of stuff to work well for us. We need protocols not platforms.

@rra

> The same goes for and the talk about or fediverse enhancement proposals.

Yes, this is a very good point. I think community collaboration to evolve the is essential. Healthy community, active participants and good governance. It is the Achilles Heel of the .

One of the initiators of FEP just made a switch to for and you might say that 2 reasons were directly related to lack of maturity in the specs and ecosystem

Sign in to participate in the conversation
Mastodon

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!