I have no experience with the last two options you mentioned, but I was of the understanding that XMPP does not have video group call functionality. Also, it has been a long time since I used XMPP at all, but syncing history between sessions was not possible to me then. These are features that would be deal breakers to miss.
History / sync is known as message archive management (MAM) & every normal modern client & server supports it. OMEMO uses same double-ratchet encryption & multiple clients as Matrix (with the same old client key dropping issues sadly). By default it does not support groups you are correct, however, FOSS Jitsi (& Zoom for that matter) is powered by XMPP under the hood & can be stood up by yourself.
Personally three of my circles have opted for separate Mumble servers for voice coms (I run one of them from my living room) as video is only ever rarely needed & the system resources is minimal. Having web cams on is seen as a chore & distraction sometimes. The only time video is helpful in my experience is screen share which is different—but screensharing is the worst tool for trying to do code pairing / debugging a terminal using upterm provides a crisper view experience, lower data/system requirements, & observers can optionally drive the remote session.
Did not know about MAM, but that sounds great. I also hosted a Mumble server for my friends for over 5 years, but it was basically never used because there existed a one-stop solution (Discord) that allowed for more stuffTM. TIL Jitsi was powered by XMPP, thanks. I personally have no problem with fragmenting functionality between different specialized applications, but it will always be a tough sell for those I know because they believe they can have it all in their cool app.
At the end of the day, communication services usefulness are upwards limited by the people you can reach through them. The need for everything to be easy and centralized for the user (ironic with respect to server federation, I know) is what has made me so hopeful for the Matrix protocol, since it is designed for allowing this while still being decentralized at its core.
One of my longer-term goals is to integrate Mumble on XMPP (others have thought about this too) since its chat is pretty shit & needing accounts to join isn’t great but or two good foundational protocols.
XMPP is better for modularity which is why everything is at extension with means the foundations are simple & easy to implement where you can build something optimized & bespoke on it like Fornite’s coms or Nintendo’s presense. It’s a little harder to understand tho since out of the box you get almost nothing—but the big servers intended for chat like Prosody & ejabberd have sane defaults.
The centralization you are referring to seems more a client issue since the protocol & servers already ‘do the things’ but it sounds like you want a single ‘app’. For community building where you consider group calls less common, both Movim & Libervia offer more than Element (note the other Matrix clients are lacking feature parity) since they both can do integrated posts like forums—where Libervia supports calendars/events too. There’s no reason a client couldn’t exist with Jitsi or Mumble integration.
Ultimately use the right tool for you—it’s just nice to dispel myths that Matrix has some special sauce or that predecessors can’t fill the same roles (while also using less resources in all directions).
I have no experience with the last two options you mentioned, but I was of the understanding that XMPP does not have video group call functionality. Also, it has been a long time since I used XMPP at all, but syncing history between sessions was not possible to me then. These are features that would be deal breakers to miss.
History / sync is known as message archive management (MAM) & every normal modern client & server supports it. OMEMO uses same double-ratchet encryption & multiple clients as Matrix (with the same old client key dropping issues sadly). By default it does not support groups you are correct, however, FOSS Jitsi (& Zoom for that matter) is powered by XMPP under the hood & can be stood up by yourself.
Personally three of my circles have opted for separate Mumble servers for voice coms (I run one of them from my living room) as video is only ever rarely needed & the system resources is minimal. Having web cams on is seen as a chore & distraction sometimes. The only time video is helpful in my experience is screen share which is different—but screensharing is the worst tool for trying to do code pairing / debugging a terminal using upterm provides a crisper view experience, lower data/system requirements, & observers can optionally drive the remote session.
Did not know about MAM, but that sounds great. I also hosted a Mumble server for my friends for over 5 years, but it was basically never used because there existed a one-stop solution (Discord) that allowed for more stuffTM. TIL Jitsi was powered by XMPP, thanks. I personally have no problem with fragmenting functionality between different specialized applications, but it will always be a tough sell for those I know because they believe they can have it all in their cool app.
At the end of the day, communication services usefulness are upwards limited by the people you can reach through them. The need for everything to be easy and centralized for the user (ironic with respect to server federation, I know) is what has made me so hopeful for the Matrix protocol, since it is designed for allowing this while still being decentralized at its core.
One of my longer-term goals is to integrate Mumble on XMPP (others have thought about this too) since its chat is pretty shit & needing accounts to join isn’t great but or two good foundational protocols.
XMPP is better for modularity which is why everything is at extension with means the foundations are simple & easy to implement where you can build something optimized & bespoke on it like Fornite’s coms or Nintendo’s presense. It’s a little harder to understand tho since out of the box you get almost nothing—but the big servers intended for chat like Prosody & ejabberd have sane defaults.
The centralization you are referring to seems more a client issue since the protocol & servers already ‘do the things’ but it sounds like you want a single ‘app’. For community building where you consider group calls less common, both Movim & Libervia offer more than Element (note the other Matrix clients are lacking feature parity) since they both can do integrated posts like forums—where Libervia supports calendars/events too. There’s no reason a client couldn’t exist with Jitsi or Mumble integration.
Ultimately use the right tool for you—it’s just nice to dispel myths that Matrix has some special sauce or that predecessors can’t fill the same roles (while also using less resources in all directions).