TelloGo VS Neko

AV1 support is already available in libwebrtc!

So when I started building Pion the target use case was to make it easier to build scalable servers. Instead of interacting with a WebRTC servers REST API to query information/load balance I wanted to have it all in one code base. It also is really useful to have Media+Transport decoupled. Lots of use cases I didn't realize grew out of that.

* Teleoperation/robotics (https://github.com/Ragnar-H/TelloGo)

* Control remote software (https://github.com/m1k1o/neko)

* Cross platform file sharing (https://github.com/saljam/webwormhole)

* Sending pre-recorded media (RTMP/HLS/RTSP -> WebRTC)

* Custom DataChannel servers/bridges (https://snowflake.torproject.org/)

Lots of other cool ones in https://github.com/pion/awesome-pion I need to update it. It has been a bit since I have looked through https://pkg.go.dev/github.com/pion/webrtc/v3?tab=importedby

Control drone over browser

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.