Is this just a docker-compose setup, or did you write the code? I see some go code in there, did you write the WebRTC server stuff yourself? If so, how come it's not published as a normal package which doesn't require docker?
I'm asking because I'm interested in remote desktop solutions, but in many cases I don't want/need docker, so any novel remote desktop utilities are interesting to me.
Although, I think about publishing the core of it as a package, fully fledged alternative to noVNC. Where X server desktop can be shared using WebRTC technology to a browser.
I think that would be nice! There are a lot of ways to approach this (I've used xpra, vnc, remote X, xrdp...) and there are pros/cons to them all. It might be useful for more people without the docker requirement :)
The other exciting thing about Data Channels is that you can send lossy/unordered messages and get flow control. You can know how much data you can send and how fast. You can build faster and more responsive data APIs that way!
Normally for this kind of thing you need an OS-level component.
There's something on the GO side but trying to find the bridge on Vue side
https://github.com/m1k1o/neko/blob/master/server/internal/we...
idk maybe somewhere in here https://github.com/m1k1o/neko/blob/master/client/src/compone...
I had to deal with this problem too with regard to remote control somehow without installing an OS-level app but that didn't happen went a different route.
Idk this is a cool project, looks like it is possible to do remote control with webrtc. And webrtc as said above can replace websocket for data transfer.
https://github.com/maxogden/screencat
ehh then again:
> On the host side the app must synthesize mouse and keyboard events on the host OS. This is the tricky part, and the only part where a custom native node addon (C++) is required.
Yet another cool project robotjs hmm
Hmm that's cool I was not aware of this thing, not surprising but still cool to find out now.