Current problem
While being able to self-host Fluxer is fantastic, I believe it could be even less complex and thrust less responsibility on the self-hoster. Currently you must deploy Fluxer in its entirety on your hardware. I would like to see a more modular approach, at least for voice/video.
Proposed change
Rather than requiring the self-hoster to deploy the entire Fluxer stack, I think it could be beneficial to allow the server administrator to use a different Fluxer instance's configuration for voice connectivity. I believe that voice/video is the most intensive service to run, and can be cumbersome to maintain.
If there were an option to point at another publicly-accessible Fluxer instance - such as the main fluxer.app instance - for pieces of the stack that a self-hoster would rather not burden themselves with, while retaining their ownership of the other pieces, this would allow more flexibility and be less daunting for a self-hoster to manage.
Voice servers specifically would be useful to: offload to avoid hitting throughput limitations, increase the amount of supported voice regions on servers that host users in various geographic locations, and offer more stability and redundancy in case of outages.
Platform
Self-hosting
Additional information
I was mostly inspired by looking at how flexible Armada is. You can choose to host the web app, the nostr relay, or the voice server, all individually. This granular approach lowers the barrier of entry for those who would like to control their most sensitive conversations, yet don't want to be burdened with the potential complications or complexity of voice servers, or any other component of the stack.