Jeremy Harris

Perhaps you could implement this in your signaling layer instead?

@junoriosity It is not my package. I am just advising on my own accord. With that in mind all I can do is point you to the docs here: https://nodejs.org/api/http.html#httpcreateserveroptions-requestlistener

I haven't tried this, but discovered a kext-less implementation (doesn't require a kernel extension) of FUSE here, that currently has 678 stars: https://github.com/macos-fuse-t/fuse-t I made a workaround myself, using Docker...

Somewhat related, and could be adapted to use werift-webrtc. I started a fork then did a rewrite in TypeScript, supporting independent data channels, stereo audio, and codec customization. It is...

> @laxian are you able to reproduce the issue with latest version? It's been happening to me. I haven't been getting disconnect events when the socket goes offline in the...

@peteashworth I'm not the maintainer but you should be able to generate a config w/ only the details that you know, and the rest should be randomized. `const config =...

If I'm not mistaken you should be able to do something like this: ```js const initialConfig = genConfig("[email protected]") const config = genConfig({ ...initialConfig, sex: "woman" }) ```

Electron probably would work since it's based on Chromium. I ran a WebRTC project in a headless Chromium container using a WebSocket connection to control it, and it was very...

@butera-simone The "easier" part for Node.js integration is the kicker; it's either unreliable (as in good luck making it work on Node.js directly) or resource intensive (if using a headless...

A long-running WebRTC connection on mobile wouldn't be sustainable. Push notifications would be far more efficient.