i think for my purposes i’m fine with hosting that through a separate service, so instead of XMPP + mumble i would run polyproto + mumble (or some other voip solution, screen sharing seems to be a decent way away in mumble)

but (as i understand it), polyproto isn’t a chat protocol per se, but more a protocol for federated message authentication. as an application of this protocol, they’re building polyproto-chat, which is a chat protocol. in theory, one could then also build a polyproto-voice so you can use the same account for both chatting and voice calls. i still think this is pretty far away, considering how young polyproto is, which is why my current vision is chat and voice as two separate services (which i also prefer because i imagine it makes the technology simpler and hosting easier)