it falls down when data needs to be sent between a browser and a dedicated server...It falls down because WebRTC is extremely complex. The SimplePeer library w

it falls down when data needs to be sent between a browser and a dedicated server...It falls down because WebRTC is extremely complex. The SimplePeer library works very well to hide the complexity of WebRTC. It works just fine for me. The big sticking point is the complexity/overhead of the setup. This might be mitigated by using the true headless modes in Chromium and Firefox. Given what I remember from installing dependencies, it should be possible to create a fairly lightweight headless fork that only has just enough to run WebRTC datachannels. So, if you don't need lots of scaling and can deal with the overhead, there is no hold-up right this moment. It's just a matter of motivation.