sctp VS aiortc

I am sure there are even more implementations that I am not aware of.

* https://github.com/pion/sctp

* https://github.com/aiortc/aiortc/blob/main/src/aiortc/rtcsct...

* https://source.chromium.org/chromium/chromium/src/+/main:thi...

* https://github.com/sctplab/usrsctp

People don't make these decisions for technical reasons only. Career wise it is a bad choice to spend your time working on pre-existing technologies. You don't become a distinguished engineer by iterating on existing technologies. You become one by being the creator of something new.

I think QUIC is great and does a good job solving the problems it was designed to solve. It is disingenuous to pretend these decisions were made only for technical reasons.

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.