rtctunnel VS aiortc

Hey HN, web-p2p-tunnel is a hobby project I built over the past month.

It enables you to expose a local web server to devices on different networks. Nothing to install on the consuming devices - just a web browser. And no server in the middle. It uses a Service Worker to intercept HTTP requests and WebRTC to tunnel requests/responses directly between consuming devices and the device running the local web server.

To use: install the web-p2p-tunnel CLI program which receives requests, reverse proxies them, and tunnels responses. See the README for details. The website is deployed using Github Pages at https://tunnel.andrewt.io/. Additionally, a signaling server is deployed at https://signal.andrewt.io/.

I've tested on a number of OSs and browsers and with simple static web sites and more complicated apps. A lot of it just works, but there are kinks and edge cases and almost certainly bugs. Let me know :) Currently, there are no TURN servers configured, so connections may fail under certain network conditions.

Motivation: I built some media features using WebRTC at my last job. It's a bit of a pain to use, but it's a powerful technology. On the media side of things, however, P2P quickly turns into more of a client-server situation w/ something like an SFU for common use cases. From my understanding, WebTransport might become the better technology for this use case. This got me thinking about use cases that would specifically benefit from the P2P aspect of WebRTC, which led me here. I was inspired in part by this project: https://github.com/rtctunnel/rtctunnel.

Excited to share the project - I think it could be a useful dev tool. Feedback appreciated!

LiveShare type application from VScode

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)

Not sure flask would work but I think https://github.com/aiortc/aiortc has an example just like what you are trying.

Context: I was making a snapchat-like filter application on webcam footage. In order to create those overlays, i used some python's opencv and dlib to locate the face and apply the overlay. As far as i know, websockets are not good for video transfer since sockets are slower so someone suggested me to use "WebRTC". So I decided to settle on this https://github.com/aiortc/aiortc python based webrtc to use my python code at the backend and use a JS front end to send the video and received the filtered image

So it seems like https://github.com/aiortc/aiortc is the obvious answer here, but I just can't seem to grok the documentation. I have run the examples successfully, but can't quite seem to tailor them to my use-case.

I'm not sure how you weren't able to find this: aiortc

You can't use Django for that, RTC is a separate protocol from HTTP. Check out https://github.com/aiortc/aiortc for a Python-based RTC stack. You write code in there which does the data processing and calls HTTP APIs or something on the Django side.