Neko VS werift-webrtc

Well here's a similar project you can look at: https://github.com/nurdism/neko

Not sure how well it would work but there’s a thing called n.eko I’ve used in the past. It’s a docker container that hosts a web browser as a website that multiple people can go to and all watch the same screen. It has adjustable resolution too so you can pick whatever works for your bandwidth. While the original version does only support a web browser you can tweak the docker config to dump you to a Linux desktop instead where you could play it in your preferred watching software. One downside to this method is it needs 2 ports forwarded for every user in addition to the ports for the site itself. here’s the link

The best implementation I have seen of this is neko. The responsiveness is good enough for real-time IMO.

github Reddit post

Share browser with friends, watch movie, Shop or do whatever together

I saw also docker image for setting up a browser that will do a sharescreen but I never tested it yet (https://www.watchparty.me/) or (https://github.com/nurdism/neko).

Another way I have been doing it is using neko it is a web browser that outputs to RTMP. You could run this on a server and then join the conference call. It would load the page and get the usual conference experience. You could then send that to a RTMP server.

You could try n.eko.

I am really excited about https://github.com/sepfy/libpeer. It has examples ready for ESP32 etc....

When working on KVS I wasn't familiar with the embedded space at all. I saw 'heavyweight' embedded where you were running on Linux. Then you had RTOS/No OS at all. I wasn't prepared for these devices at all. If we can make WebRTC work in the embedded space I think it will really accelerate what developers are able to build!

Remotely driven cars, security cameras, robots in hospitals that bring iPads to infectious patients etc... Creative people are building amazing things. The WebRTC/video space needs to work harder and support them :)

-----

I love how diverse the WebRTC space is now. Outside of this implementation you have plenty of other options!

* https://github.com/shinyoshiaki/werift-webrtc (Typescript)

* https://github.com/pion/webrtc (Golang)

* https://github.com/webrtc-rs/webrtc (Rust)

* https://github.com/algesten/str0m (Rust)

* hhttps://github.com/sepfy/libpeer (C/Embedded)

* https://webrtc.googlesource.com/src/ (C++)

* https://github.com/sipsorcery-org/sipsorcery (C#)

* https://github.com/paullouisageneau/libdatachannel (C++)

* https://github.com/elixir-webrtc (Elixir)

* https://github.com/aiortc/aiortc (Python)

* GStreamer’s webrtcbin (C)

See https://github.com/sipsorcery/webrtc-echoes for examples of some running against each other.

This is not true, there are actually multiple WebRTC implementations in different languages besides the reference library: aiortc (python), libdatachannel (C++), sipsorcery (C#),webrtc-rs (rust), werift (Typescript), and Amazon Kinesis (C)

There's a native implementation that requires no binaries here: https://github.com/shinyoshiaki/werift-webrtc

Maybe I'm missing something but how is this one preferable?

Lots of great WebRTC implementations exist. Do you want to stick with node.js?

I am a big fan of https://github.com/shinyoshiaki/werift-webrtc it is pure Typescript.

Check out https://github.com/sipsorcery/webrtc-echoes for all the other implementations.

werift(TypeScript)

https://github.com/shinyoshiaki/werift-webrtc (Typescript)