This problem is reminiscent of the web-browser conundrum. Perhaps the project is, by its nature, just too ambitious to be left to a small handful of volunteers. An organization, with reputation (and maybe money) at stake, needs to take the reins.
Currently, Flatpak still uses PulseAudio even if a host system uses PipeWire. The problem with that is that PulseAudio bundles together access to speakers and microphones—you can have access to both, or neither, but not just one. So if an application has access to play sound, it also has access to capture audio, which Wick said, with a bit of understatement, is “not great”. He would like to be able to use PipeWire, which can expose restricted access to speakers only.
Oof. Seems that snap (to take the obvious comparison) separates these two permissions. As it should.




























Horse door bolted. But better late than never.