4 ms·

As someone who works for a company thats developed their own end to end conferencing stack (utilizing webrtc stack on the client side and all custom conference

As someone who works for a company thats developed their own end to end conferencing stack (utilizing webrtc stack on the client side and all custom conference servers and sfu on the backend), what would be the benefits of adding Matrix support and how exactly would that be done (at a high level)? What would the benefits to users be? Trying to understand what all the hype is about here, and whether or not this would be a venture to pursue and what the business justification would be.

Arathorn 3y ago
Using Matrix would mean: * You get best practice audited (in the near future) end-to-end encryption * You get decentralisation if your users want to host the stack themselves * You get bridges to other systems (although not many FOSS voip bridges for Matrix exist today, admittedly) * Similarly, you get an open standard API on which you and others can write bots/apps and other extensions to add new functionality, and benefit from the wider ecosystem * You get some preexisting clients like Element Call to build on.
- yobid20 3y ago
  Well, we dont want e2ee because then we cant decode audio and transcribe, or record meetings. All of which are high demand user requirements. We dont want decentralisation either for the same reason. We dont interop with other video conference systems other than asterisk for dial in/out. And the ones that we might consider doing that for dont support matrix either. We want a fully integrated system for our users so i dont see external clients being a thing. An open standard api is a plus but in my experience there's always something they fall short on requiring something custom. This is why i find it difficult to see where matrix could improve anything for us. Trying to find some benefit but I really don't think there is one other than maybe marketing and saying we play nice with open source or open standards.

Arathorn 3y ago

Using Matrix would mean: * You get best practice audited (in the near future) end-to-end encryption * You get decentralisation if your users want to host the stack themselves * You get bridges to other systems (although not many FOSS voip bridges for Matrix exist today, admittedly) * Similarly, you get an open standard API on which you and others can write bots/apps and other extensions to add new functionality, and benefit from the wider ecosystem * You get some preexisting clients like Element Call to build on.

yobid20 3y ago
Well, we dont want e2ee because then we cant decode audio and transcribe, or record meetings. All of which are high demand user requirements. We dont want decentralisation either for the same reason. We dont interop with other video conference systems other than asterisk for dial in/out. And the ones that we might consider doing that for dont support matrix either. We want a fully integrated system for our users so i dont see external clients being a thing. An open standard api is a plus but in my experience there's always something they fall short on requiring something custom. This is why i find it difficult to see where matrix could improve anything for us. Trying to find some benefit but I really don't think there is one other than maybe marketing and saying we play nice with open source or open standards.