Me after completing exactly zero (0) tasks on my to do list
netchami
TIL that XMPP is defined in an RFC. You're correct, I wasn't aware of that. I really don't understand why the IETF take such a decision though. I don't know why these guys are defining high-level protocols for things like messaging at all.
But back to your earlier points:
For example you can't have end-to-end encryption if you use a non-standard protocol
This doesn't make any sense whatsoever. Matrix has E2EE while using a "non-standard" protocol. So does Signal, in fact, it created the strongest E2EE protocol out there.
VC startups like Matrix only increase fragmentation of the ecosystem
Every new project that is created increases fragmentation. So does Revolt, Discord, Skype, WhatsApp, Signal, Telegram, etc. These all use "non-standard" protocols.
Also, the author of RFC 6120 is a Cisco employee, how is a multinational corporation better than a VC-funded startup? XMPP is an open standard, just like the Matrix protocol. It doesn't matter who created it.
That doesn't make any sense
Nah, they have a clause in their EULA which allows this, it's ridiculous. Piracy is the only solution.
Who defines standard internet protocols and how is XMPP one of them??? "Standard internet protocols" are DNS, HTTP, TLS, etc.
VCs suck, but Matrix is open source, everyone can self-host their own server, write their own client or even fork the entire protocol.
It isn't proprietary either
What part of Matrix is proprietary? It's not an app, instead, it's an open protocol that can be used by anyone to build a messaging app or host a server.
I like your approach