Modern XMPP project discussion - 2025-11-25

Funnier question is: how Transcoding SFU would reencode encrypted streams?

> separating mumble/xmpp for audio and chat allows a reduced memory footprint for users who don't want audio. Integrating everything into a superapp ends up in bloatware its a big point for people wanting to move off of platforms like discord though, people don't want to use multiple apps for communication, and I don't understand the memory footprint argument, wouldnt it not have to use anything if you dont use the functionality? and using multiple apps for communication is a bigger memory footprint for those users that do want both which I think is probably a majority. plus im sure theres always gonna be clients that cater to minimalism rather than trying to be modern if you want something lightweight. ↺

>> separating mumble/xmpp for audio and chat allows a reduced memory footprint for users who don't want audio. Integrating everything into a superapp ends up in bloatware > its a big point for people wanting to move off of platforms like discord though, people don't want to use multiple apps for communication, and I don't understand the memory footprint argument, wouldnt it not have to use anything if you dont use the functionality? and using multiple apps for communication is a bigger memory footprint for those users that do want both which I think is probably a majority. plus im sure theres always gonna be clients that cater to minimalism rather than trying to be modern if you want something lightweight. 💯 ↺

hueso, not necessarily, codepaths you don’t use are just dead code in the executable, they don’t use memory unless you actually use them.

sure. that's how it should be, it can be done like that, but often times that's not the case. devs don't care about that and end up with some discord like electrum monstruosity

So let's care

BTW, next release of HedgeDoc will render XMPP URIs correctly: https://github.com/hedgedoc/hedgedoc/issues/6099 :D

</slight-offtopic>