Matrix is a protocol, Discord is a system. For want of better terms. Perhaps you could compare git with Github or Gitlab. Matrix might be able to fulfil your requirements but you don't state them.
Why not start with: "I need a communication system for my organisation that satisfies the following criteria and I accept that there is no ideal and I am willing to reform my requirements as I evaluate the options available"
* End to end encrypted
* Check up on governance: Local requirements
* Media
* Text
* Voice
* Video (plus voice)
* Supports emoji
etc, etc.
What do you really want and are you prepared to put some real work in to actually evaluate some possibilities? If not, then stick with Discord. It probably won't kick your kitten but it now belongs to Microsoft who also own LinkedIn and sadly themselves.
I've evaluated Rocket Chat, Mattermost, Zulip, and Element+Synapse at various points over the last year and a half. That included compilation and deployment on AWS instances. I've done leg-work.
Matrix's official server and client are often touted as a competitor to other team and community-oriented chat platforms by its proponents. As a signal competitor it's solid enough, but in the community space it fails to be competitive.
I'm really hoping to see Matrix mature more, and codify moderation apis in order to keep the protocol client/server agnostic for all standard use-cases.
The Matrix documentation itself admits that the community-management portion of the standard is underspecified.
Why not start with: "I need a communication system for my organisation that satisfies the following criteria and I accept that there is no ideal and I am willing to reform my requirements as I evaluate the options available"
etc, etc.What do you really want and are you prepared to put some real work in to actually evaluate some possibilities? If not, then stick with Discord. It probably won't kick your kitten but it now belongs to Microsoft who also own LinkedIn and sadly themselves.