server VS neko

Amazing work! The WebRTC community needs something like this so bad. Not only will this push a bunch of users toward self-hosted/free software but will also inspire others to build cool things :)

If/when you hit scaling challenges I would love to help! I maintain github.com/pion/turn and github.com/pion/webrtc. You can see that with how screego[0] does it.

Happy to help however I can (even if not using Pion!) One of the reasons I built it was so that I could put my TURN and Signaling server in the same process. It makes it way easier to tie your auth together for signaling+TURN. Then if you do go down the SFU route lots of interesting things you could do.

[0] https://github.com/screego/server/blob/e845b3d29c4b5794ed10f...

Check out ScreeGo : https://github.com/screego/server

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.