|
|
|
|
|
by Arathorn
1476 days ago
|
|
What you can do with Element is: * Have signal-style end-to-end encryption by default, if you care about keeping your data secure on the server. * Pick from a huge range of alternative clients, including hooking up custom ones thanks to Element being built on the open Matrix standard. For instance, if you wanted to plonk an Intercom-style chat box on your website which funnelled into your support chatrooms, there are a a bunch of different matrix-as-chatbox clients you could use * Bridge to other platforms as if you were using them natively (as per the sibling comment) - e.g. if you already have other chat systems flying around the place, you can easily unify them in Matrix * Talk to people outside your company. If you care about collaborating with external people (other developers; customers; partners; suppliers; sibling companies etc) then Matrix's intrinsic decentralisation means you can just talk to them via the public Matrix network. For instance, I spend my life collaborating with folks on the mozilla, KDE, GNOME, Ansible etc Matrix servers without having to think (let alone manage a million different tabs and identities and crappy clients for their various communities). So, that's the pitch. |
|