OBS-studio-webrtc VS neko

For those of you who are overwhelmed with the official IETF document, WHIP (sometimes known as WISH) is an open standard that you can use right now for your WebRTC based ingestion. You can use it today with open source software such as GStreamer or OBS (fork) as a way to publish your content with WebRTC.

Download the OBS WebRTC publisher

There are a few other WebRTC based solutions. There's a fork of OBS that allows streaming out using WebRTC. I think that only supports millicast.com, which I believe is not open source. There are a few other servers that handle WebRTC, but I don't know if any are WebRTC.

What you'd want is for OBS to output the WebRTC stream itself, rather than going through the webcam interface for this. This is not natively available, but there is a project that claims to do this: https://github.com/CoSMoSoftware/OBS-studio-webrtc

Related: a fork of OBS Studio with WebRTC support

https://github.com/CoSMoSoftware/OBS-studio-webrtc

I personally use neko-rooms with my friends for this purpose. Just let's all share a browser in a browser with plenty of options (Firefox, Chromium, Brave, etc.). You can also just use standard neko if you don't need multiple rooms.

Hey, you do you. It just sounds like an expensive way to avoid owning the hardware you want to debug to me.

Also, not to burst your bubble, but there are a few projects out there that do more-or-less what you're describing:

- https://store.steampowered.com/remoteplay/#together

- https://github.com/m1k1o/neko

If you're having fun, then continue by all means. I've just been nerd sniped by your cloud costs and I'm having flashbacks to seeing six-figure monthly AWS bills at startups that refused to buy their own GPU compute.

You could spin up something like Kasm Workspaces, Neko or Docker Webtop.

I ran into neko https://github.com/m1k1o/neko recently which has similar. It's more application centric than desktop centric, but both offer multi-player experiences & I just think that is the absolute coolest.