My experience with Matrix/Element and the various standard-compliant Matrix chat clients, in an ISP environment, is that it's totally possible to set up a rock solid replacement for Slack within an organization that has a person on staff to spend some cycles setting it up, and periodically maintaining it.
We don't have any major technical challenges or problems running our own Synapse daemon server. It's a debian stable xen PV VM stored on a LVM logical volume, so easily moved between hypervisors, or cloned, if ever necessary. It runs at a load average of 0.01.
In my specific ISP environment it's the same person that admins the X.509 private root CA PKI so we're well equipped to deal with running it in a purely intranet environment with no access to the global routing table.
For widespread non technical random end user use? Totally agreed it's not ready yet.
An "internally-run-Slack" is definitely a great use case for Matrix in its current form. I don't own a business, but if I did, I would almost certainly consider running my own Synapse server, just to have a stronger guarantee that internal chats stay internal.
Yes at my bigco they've set up a whole matrix (rebranded) service. Great. Only thing I miss is some kind of 'ephemeral chatroom' option, where nothing is saved or expires after some time. Some conversations are not worth saving and wading through all the chat logs to find some stuff can be painful.
Also I like the other tools' (cisco jabber and some others) option to save chat logs in exchange folders, so you have local search indexation/capabilities.
On the other side, I'd also like a button to record a whole conf-call, so minutes of meetings can be backed up with the actual conversation. Yes, how 'trusting' of me...
We don't have any major technical challenges or problems running our own Synapse daemon server. It's a debian stable xen PV VM stored on a LVM logical volume, so easily moved between hypervisors, or cloned, if ever necessary. It runs at a load average of 0.01.
In my specific ISP environment it's the same person that admins the X.509 private root CA PKI so we're well equipped to deal with running it in a purely intranet environment with no access to the global routing table.
For widespread non technical random end user use? Totally agreed it's not ready yet.