3 ms·

What the assumed time frame for the switch? And once it happens, will it be a standard feature of synapse to deploy your own voice/video server?

• Arathorn 4y ago
  I'm guessing it's about 1-2 months away. The hard bit is that we need to effectively have Element Call share the same matrix client as Element itself does, in order to embed Call into Element effectively. We call this matryoshka embedding, and it's looking promising to get it working in the next week or two, and then will need to actually update all three Element clients (Web, Android & iOS) to support it. Obviously folks can also just click into a standalone Element Call to make it work (plus Hydrogen is also adding native Matrix calling). Element Call doesn't currently need any custom server - it just uses your existing homeserver; Synapse, Dendrite, Conduit etc. However, it only scales up to 7-8 users - to go beyond that we'll need to add a SFU, which we're also working on.
  • panick21_ 4y ago
    Thanks. And thanks for all the great work as well.
  • anticensor 4y ago
    A MCU or a virtual apex could be better in order to ensure everyone hears the same thing. And a virtual apex combined with large events could also provide a decentralised persistence layer.
    • Arathorn 4y ago
      We're going for a hybrid SFU/MCU architecture - c.f. https://2021.commcon.xyz/talks/extending-matrix-s-e2ee-calls-to-multiparty https://2021.commcon.xyz/talks/extending-matrix-s-e2ee-calls...