SpacingBat3

> I just noticed that Signal Desktop exhibits this same behavior if run under native Wayland, suggesting it might be an Electron issue. I suspect this is more or less...

> (...) Disabling the built-in Content Security Policy **does not** seem to fix this issue. If so, that would be an issue within the Discord itself. After all, with CSP...

Right now, none of the builds are signed. This is mostly there's no integrated way in the Forge to sign (most) Linux distributables. And I'm not going to buy and...

Also check [microg/GmsCore#1876](https://github.com/microg/GmsCore/pull/1876).

As there's new location stack which isn't based on UnifiedNlp, I don't expect this PR to be maintained anymore unless there will be some development around making GmsCore use UnifiedNlp...

I feel like this is more a limitation of Discord, and tinkering with it is bypassing it, which I'm not sure if I'm okay with to implement within my client...

@NolonQ For some time (much before Nitro got so much intrusive and Discord got the entire UI redesign) I had plans not to implement any Nitro features, the goal was...

Well, it is Chromium engine that manages it, Electron does not expose any APIs to create or manage audio streams used for both input and output AFAIK (they barely expose...

Possibly, I guess Electron doesn't even have to leak any kind of the APIs to implement this, they just need to handle renaming the streams. But given `--force-audio-share-support` is more...

Also a bit related (yet not around implementing exactly what you mention/want) issue in Electron bug tracker: https://github.com/electron/electron/issues/27581.