Matrix doesn’t have multiple standards, it only has the one? Certain servers expose older API endpoints for backwards compatibility with old clients, but that’s all. The spec is standard and relatively stable.
Likewise, it is very much a federated protocol - dunno where you got the idea that it isn’t.
But, yeah, spec changes do take a while to get accepted/implemented.
Standards as in parts of the spec, as you said in the original reply:
the new MatrixRTC spec
Which is a fork of the WebRTC protocol and another “standard” on top of the REST HTTP protocol.
I should have been more specific with my language, it is federated, but specifically messages (events) are a distributed DAG, and I find the Matrix protocol overly generic for a replacement for something specific like Discord.
The end goal of Matrix is to be a ubiquitous messaging layer for synchronising arbitrary data between sets of people, devices and services
Matrix doesn’t have multiple standards, it only has the one? Certain servers expose older API endpoints for backwards compatibility with old clients, but that’s all. The spec is standard and relatively stable.
Likewise, it is very much a federated protocol - dunno where you got the idea that it isn’t.
But, yeah, spec changes do take a while to get accepted/implemented.
Standards as in parts of the spec, as you said in the original reply:
Which is a fork of the WebRTC protocol and another “standard” on top of the REST HTTP protocol.
I should have been more specific with my language, it is federated, but specifically messages (events) are a distributed DAG, and I find the Matrix protocol overly generic for a replacement for something specific like Discord.