native-messaging-deno VS Screenshare-with-audio-on-Discord-with-Linux

You can use a Native Messaging host to run local code controlled from the browser. See native-messaging-deno for a general purpose and extensible solution and deno-server where Deno's serveTls is dynamically started to run a local application, stream stdout from the application to the browser, then stop the local server.

I'm basically trying to do this https://github.com/guest271314/native-messaging-deno/blob/local-server-dynamic/local_server.js without the issue with deno executable increasing CPU to over 90% when streaming, and without carrying around the rest of Deno that I will not be using. Building deno requires using Rust toolchain which is over 1GB to install before we even begin building anything, which is non-trivial to do.

https://github.com/guest271314/native-messaging-deno/tree/local-server-dynamic.

Python https://github.com/guest271314/native-messaging-python, Deno https://github.com/guest271314/native-messaging-deno, Bun https://github.com/guest271314/native-messaging-bun, Node.js https://github.com/guest271314/native-messaging-nodejsNative Messaging hosts

I'll check in a few minutes. This is the source code I use that shows N GB "VSZ" https://github.com/guest271314/native-messaging-deno and the server I will be using https://github.com/guest271314/native-messaging-espeak-ng/blob/deno-server/deno_server.js.

We can create virtual microphones, cameras, etc., e.g., and capture those devices using Web API's; see https://github.com/guest271314/SpeechSynthesisRecorder/issues/17, https://github.com/edisionnano/Screenshare-with-audio-on-Discord-with-Linux. See also --use-fake-device-for-media-stream, --use-file-for-fake-video-capture flags on Chromium-based browsers

Chromium and Chrome refuses to capture monitor devices on Linux. Read this https://github.com/edisionnano/Screenshare-with-audio-on-Discord-with-Linux README and the README at https://github.com/guest271314/captureSystemAudio very carefully. At best you can capture tab audio, not whatever is output to speakears and headphones, in spite of the systemAudio constraints, which is poorly named, and actually misleading.

Screen sharing with audio in Discord works fine.

If you are actually trying to record output to speakers and headphones, not just microphone input see https://github.com/edisionnano/Screenshare-with-audio-on-Discord-with-Linux, https://github.com/guest271314/captureSystemAudio.

This github project does a great job of explaining the problems with discord screensharing on linux (as well as a solution). It also mentions to a standalone project that functions as a temporary replacement for discord screen sharing if you install the dependencies (e.g. Pipewire).

Also I see all this work put in to seemingly unify the development processes between two different operating systems that somewhat undoes features that android already had, so i have to assume that this was done so android and ios could be updated with the same features simultaneously, but we already see what that looks like - a bunch of bugs on different android hardware and versions. And in all this time that this process to unify the development of the mobile app was worked on, there's a feature in the voice & video recommendations on the discord feedback website that has by far surpassed every other request in that section as something the community actually wants, a feature that has gotten daily comments for over 2 years, which is to fix the sound when sharing an application in linux - a process with a pretty thoroughly documented solution here