… and on many of them I complain again that they made a whole new project instead of just using and contributing to Jitsi , which the FSF created expressly to counter Zoom/Teams :/
At first, I wrote “Element/Matrix” and decided to not be too pedantic… But if you want to be complete: the messaging protocol is, of course, Matrix. You could say there is actually no such thing as a Matrix server either, because it’s a protocol. The server must probably be Synapse-based, I guess. But there is an “Element-based server” in the sense that the web interface of Tchap (and phone apps) are very clearly forked from Element, which is what I meant.
Visio is based on LiveKit, which Element Call is also based on (as far as I understand). It lives outside of Tchap. The DINUM never mentioned it was based on Element Call. Do you have additional information? (Not that the difference matters much I think)
You could say there is actually no such thing as a Matrix server either, because it’s a protocol.
A Matrix server is a server that uses the Matrix protocol. You could be more precise and say Synapse but that excludes community-developed forks like Continuity, Contunuwuity, Tuwunnel, etc. etc. So yes, I maintain that is the “correct” terminology.
Actually, there’s also an official Jitsi server (called Webconf). And there’s another Big Blue Button one. I think Visio has features not available in Jitsi though, like AI-produced transcript of the call.
I guess. There must be a reason for them turning to something else than Jitsi given they already had that running (and the French service responsible for that, DINUM, is surprisingly extremely open-source friendly for a state service), but I don’t know which one.
… and on many of them I complain again that they made a whole new project instead of just using and contributing to Jitsi , which the FSF created expressly to counter Zoom/Teams :/
It’s not a new project, it’s just skinned Element. Jitsi does not have the features of Element.
Tchap is the Element-based server. Visio is a different thing. Although you can trigger Visio from Tchap (like you can do it with Jitsi from Element).
No such thing as an Element based server. The server is Matrix. Element is the app. Visio is not a different thing, it’s just Element Call.
At first, I wrote “Element/Matrix” and decided to not be too pedantic… But if you want to be complete: the messaging protocol is, of course, Matrix. You could say there is actually no such thing as a Matrix server either, because it’s a protocol. The server must probably be Synapse-based, I guess. But there is an “Element-based server” in the sense that the web interface of Tchap (and phone apps) are very clearly forked from Element, which is what I meant.
Visio is based on LiveKit, which Element Call is also based on (as far as I understand). It lives outside of Tchap. The DINUM never mentioned it was based on Element Call. Do you have additional information? (Not that the difference matters much I think)
A Matrix server is a server that uses the Matrix protocol. You could be more precise and say Synapse but that excludes community-developed forks like Continuity, Contunuwuity, Tuwunnel, etc. etc. So yes, I maintain that is the “correct” terminology.
Sure, if you want… ¯\_(ツ)_/¯
Aww, man… I just got þe popcorn out.
Actually, there’s also an official Jitsi server (called Webconf). And there’s another Big Blue Button one. I think Visio has features not available in Jitsi though, like AI-produced transcript of the call.
It is actually not hard to extend the software. I, for example, set up automatic uploading of cal recordings to a Peertube instance.
I guess. There must be a reason for them turning to something else than Jitsi given they already had that running (and the French service responsible for that, DINUM, is surprisingly extremely open-source friendly for a state service), but I don’t know which one.