neko VS werift-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.

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.

Check out https://github.com/m1k1o/neko. I've been running it for a few months and am super happy with it

Depending on how you want to achieve this, you could use a combination of OBS + Restreamer or OBS + Project-Lightspeed. Another solution would be to use more specific solutions like neko

Fork of neko; differences can be seen here: https://github.com/m1k1o/neko/compare/master...wanjohiryan:q...

Commit messages seem like a bit of a mess at first glance, but otherwise seems like a really cool project!

Would love projects which allows me to use together with my partner, such as Neko ( https://github.com/m1k1o/neko ) or OwnCloud.

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)