We use matrix alongside Telegram for Dublin Linux and the Linux Lads podcast. To minimize maintenance, we took the following steps:
- we use Conduit, it’s performant and uses a single binary (we changed from Synapse after the instance broke and needed to be redeployed if i remember correctly). On the bad side, Conduit doesn’t have all the features that Synapse has, but it’s being actively developed.
- we don’t accept registrations, anyone joining the rooms have to have an account on some other instance (this was done after we got suddenly swamped by bots)
- we use t2bot as a bridge between Matrix, Telegram and Discord
This limits the needed maintenance and enables us to run the server on a small VPS.
The biggest issues we encounter are bridge disruptions. These can sow massive confusion in the conversation, I can’t recommend bridges for a high frequency work environment. (I have a similar experience in a separate project, where they use self-hosted bridge to link IRC and Discord though, so it’s not just a Matrix problem).
Separately, as a Matrix user, I don’t think that the technology is ready for a non-motivated user, specifically because you need to read the manual to understand verification, spaces etc. As well, not every feature is present or works the same in different clients and servers.
In my opinion, if you want a messaging system that can get people talking without friction, I don’t think Matrix is it. I don’t think that there currently is a good open source solution, something with the functionality of Discord, simplicity of Telegram and a self-hosted option.
(as an illustration, whenever i run Nheko, I get this message, no matter how many times I try either of the options. )
