I want to like Matrix, but this is currently the most painful point, for me. There are very few mature clients, so they don't serve as many niches or specific tastes as IRC clients.
> I can't see how IRCv3, if it ever lands, can compete with this. It's years (decades?) behind at this point.
Not sure what you mean by "landing". Many specs are already implemented, deployed, and used in the wild.
> And if it lands a spec which is equally capable as Matrix, how can it ever be compatible with "the old IRC"?
Every IRCv3 spec is designed with backward compatibility in mind, so old clients are not left behind, they just don't benefit from the new features. The main mechanism for this is a capability negotiation when clients connect.
the main matrix homeserver blocks you from federating with them if you violate their CoC and kicks all matrix users from your room
In my opinion that doesn't really matter. matrix.org is "just another homeserver" - it just happens to be one with a large amount of Spaces and rooms, and thankfully federation doesn't orbit around matrix.org nor does it depend on that.
There are plenty of other homeservers which federate with each other quite happily. I've seen some rooms which have a policy of not allowing users with a matrix.org account, because they disagree with the matrix.org CoC/policies/actions, and that's also fine, because the nature of the matrix protocol allows that freedom. If a person wishes to stick with matrix.org, well, they have that choice. If a person has a homeserver which gets booted from federating with matrix.org, that's also fine - the problem will eventually be routed around by federating with plenty of other homeservers. This happens already.
If you use the main Matrix homeserver and you're in a room hosted on another server when this happens, does your client show a helpful message like: "Sorry, you're not allowed to be in this room any more, because the people hosting the room committed the following thoughtcrime: $REASON"?
I worry that it will instead just look like some generic network error message, with the remote server being tacitly deemed an un-place full of unpersons. Down the memoryhole it goes.
The question isn’t “If this can work with Matrix why not XMPP?”, the question is “Will Matrix have the same issues as XMPP?”
Success is adoption. Enough users to break the network effect.
Signal is currently a good example of roughly the amount of users you need to start breaking the effect. So that's what success looks like. A very low bar version of it.
Darn hippies with their inclusivity and community standards!
People like you is why I long left this forum and IRC servers in general. You give the tech industry a bad name.
You might be assuming everyone else has the same relationship with the words that you do and this could be a mistake.
The new IRC is Matrix, or at least for now. For me at least, it fullfills the same needs:
- deploy your choice of server-software on your preferred server.
- use your preferred client to connect to your preferred server.
- allow communities to manage themselves in a decentralized manner, without any San Fransisco-based big-tech company imposing their CoC, ToS or view of "diversity" upon them.
And it does so in a way which is mobile-friendly and supports all the "modern" additions to IM which normal people have come to expect. I can't see how IRCv3, if it ever lands, can compete with this. It's years (decades?) behind at this point.
And if it lands a spec which is equally capable as Matrix, how can it ever be compatible with "the old IRC"? Myself, I'm still running my IRC network and servers, but they are bridged to Matrix and I encourage the community to move there too. And thus ends my interest in IRCv3.
All in all, this seems like a lot of spec-work going into a what is surely going to be a doomed venture.