i find it really funny that discord has its own fucking browser with raccustom extensions only for it to be………worse than opening it up in the browser.

genuinely. what the fuck.

there’s an entire set of Just Discord Things that are Only Problems in the desktop app And Not The Browser like what do you mean you made chrome unable to support hi-res audio devices but only when it’s not like a youtube embed or sth like that, what do you mean you removed krisp support

apparently krisp being missing is DRM bullshit that fails on nixos. which would also not be an issue if they used like fucking RNNoise which is Good Enough for me

@charlotte nowadays patching the web app to support the good desktop things is actually better than using the desktop app it’s crazy

@charlotte oh yeah didn’t they have to patch out the drm for ages

@tauon it certainly doesn’t work at the moment

@charlotte waitwhat? krisp works fine on my machine.

but also i use vesktop which actually embeds the web client with some plugins restoring desktop functionality.

does the krisp module really depend on DRM on the desktop version only, and therefore is only an issue with the official desktop client?

‘cause. lol. lmao, even.

@charlotte oh wait yes. this is the point of the thread.s orry i only read one post on my timeline lmao

@charlotte why don't they admit defeat and throw the user API wide open? #lang_en

@sodiboo it works perfectly fine in the browser. on firefox even!

it also supports wayland screen sharing. because lmao.

@charlotte i remember someone having to patch something, might’ve been a mod developer or something, i’m not sure

@ellenor2000 so the thing with krisp is that it runs in the browser just fine. the native module fails. but the (presumably wasm?) version works perfectly fine with zero issues. as such there really was no reason to do this

@charlotte @sodiboo as far as I can tell the one thing that doesn't work (out of the box) in a normal browser is screen sharing with audio

Some of these are also just decidedly problems with discord Reinventing The Wheel

The hi-res audio problems on discord are 100% due to their one Linux dev not understanding/being paid enough to care about edge cases that chrome handles flawlessly. Of course they *literally have code that makes the browser play audio from discord-internal sources* so it's literally just reinventing the wheel

@novenary @charlotte oh yeah. wait what why don’t browsers implement that.

i mean i know why. i get that audio on linux is completely disjoint from graphics.

still, why don’t browsers let me share audio and just pick a source? surely the web standards include audio-video desktop capture, since windows and mac both do it just fine?

@sodiboo @charlotte they do and it works, discord is just extremely stupid about it but i have a userscript that lets me screenshare with audio just fine

@novenary @charlotte oh. browsers do allow screensharing with audio on wayland/pipewire?

i assumed it was a browser issue because discord isn’t the only app i’ve had this issue with

@sodiboo @charlotte ok apparently it's a bit weird and the functionality is incomplete in browsers (absent in firefox, not supported on linux for chromium; https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/getDisplayMedia)
the script relies on a loopback device (not sure if this is actually necessary, probably not) and bridges the missing functionality and it just works

script: https://wank.party/jOuQ.txt (based on https://github.com/edisionnano/Screenshare-with-audio-on-Discord-with-Linux, fixed up by @bb010g)
to create the loopback device: `pw-loopback --playback-props='media.class=Audio/Source' -n virtmic -c 2`

Although admittedly it's an edge case in the sense that it doesn't come up on a system with default config but it's very obviously a bug on their end (not picking a sample rate/sample buffer size combo that it can work with)