umurmur VS aiortc

>...its server side is still written on Qt, which requires hundreds of megabytes of additional libraries to build it up.

See:

https://github.com/umurmur/umurmur

I've tried to make this argument in the past and gained no traction. What I did instead was to create self hosted chat things as a fallback for the times when Discord or Slack have a green status page but their applications fail to operate. Even light-weight daemons like uMurmur [1] or devzat ssh-chat can be handy in a time of need if a quorum know to fall back to it. Self hosted tools are also handy when one wants to share links or text that should not be on 3rd party sites forever and for eternity

[1] - https://github.com/umurmur/umurmur/wiki/Configuration

[2] - https://github.com/quackduck/devzat

Adding a more private self hosted option, there is uMurmur [1] which is light-weight enough to run on a Linux router. One of the mobile apps that works with it is Mumla.

There is of course the full blown Murmur [2] install that works a little more like Discord in that people can create channels and there is a permission system.

[1] - https://github.com/umurmur/umurmur/wiki/Configuration

[2] - https://wiki.mumble.info/wiki/Main_Page

For the other layers one can front-end IRC with TheLounge [1][2] or Convos [3][4]. TheLounge only persists history in private mode meaning that users are created in that front-end and chat messages are in Redis. For small networks or groups of friends this is probably fine.

Notably missing is voice chat. I use the Mumble client [5] with the Murmur or uMurmur [6] server which is light-weight enough to run on ones home router. I use it on Alpine Linux, works great. It's not a shiny and attention grabbing as Discord but probably fine for everyone else. For people to create their own voice channels would require the full-blown Murmur server.

[1] - https://github.com/thelounge

[2] - https://thelounge.chat/

[3] - https://github.com/convos-chat/convos/

[4] - https://convos.chat/

[5] - https://www.mumble.info/

[6] - https://github.com/umurmur/umurmur/wiki/Configuration

I suppose people should decide for themselves if they take the word of a centralized service. Convenience is a factor after all.

For those that have small circles of friends they wish to chat with and minimize the number of ISP's their traffic traverses, I would suggest tinkering around with uMurmur [1] There are pre-built packages in several operating systems package managers. The configuration is dirt simple [2] and the daemon is very light weight, designed to run on home routers. Use certbot to generate LE certs or just use self-signed. One TCP and one UDP port must be forwarded to the daemon, default port being 64738. One can set a server-wide password to keep strangers off of it, or set passwords per-channel.

uMurmur is not E2EE but if it is running on your own router and you are talking with your friends that you know and trust then maybe that is less of an issue. The mobile client is Mumla. Just put in the IP or hostname of the uMurmur instance.

[1] - https://github.com/umurmur/umurmur

[2] - https://github.com/umurmur/umurmur/wiki/Configuration

I like https://umurmur.net/ since it can run totally headless at the cost of some of Murmur's features. Mainline Murmur (the Mumble server) requires QT5 and mDNSResponder and various DB drivers and even D-Bus if you look at it crossways

I believe quite a few people use umurmur for stuff like this. Note that it's encrypted and I don't believe that can be shut off, so don't run it over, say, HamWAN, but I don't imagine that was the plan anyway.

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.