docker-jitsi-meet

Jitsi Meet is pretty good for video, and relatively easy to self-host, though you'll need some decent resources for it. The docker-jitsi-meet project[0] can get you started quickly Signal's "source available" infra can be self-hosted but it's huge effort and relies on a bunch of cloud-specific services which need to be replaced with self-hostslable alternatives. It's also extremely poorly documented and the code quality is fairly mediocre. I wouldn't recommend trying to host Signal infra yourself; it can be done; I've done it at work and it took some months of effort, and maintaining it is a nightmare (or was, then at least) because they'd only push one huge update to GitHub quarterly or less often. [0]https://github.com/jitsi/docker-jitsi-meet

Zoom is the Windows of conferencing apps: It is the most popular one, so researchers actually look at it and say it's shit, but the alternatives aren't much better [1]. [1] Just one example: https://github.com/jitsi/docker-jitsi-meet/blob/master/CHANG...

NYC could set up a jitsi instance. https://github.com/jitsi/docker-jitsi-meet#quick-start

Yes... but in one case the software is entirely FOSS and readily deployable via a docker image. The Zoom server is not FOSS, or even accessible through their GitHub. https://github.com/jitsi/docker-jitsi-meet

I am also doing this, so I'll take the liberty of answering. There's a turnkey docker which should take a few minutes to install: https://github.com/jitsi/docker-jitsi-meet Put nginx in front of it with Let's Encrypt and it shouldn't take more than half an hour to set up. After that you basically get a clone of meet.jit.si. I'm using it with the low level JS library in order to build a product that contains video chat. There was a bit more messing about for me, but only a bit.

1. Yes, it has pretty high CPU usage unfortunately and that’s despite the attempts of Jitsi to offload h264 encoding onto the clients. You could in theory lock it to standard definition video though which would reduce CPU usage a lot. 2. We did not on this instance but we did using their Docker instance which was very straightforward to setup: https://github.com/jitsi/docker-jitsi-meet#jitsi-broadcastin... I don’t believe it needs a VM per conference - maybe a ffmpeg process per instance? Here's the Jitsi architecture which best I can tell shows JIBRI (recording part) as a separate, single container: https://i.imgur.com/oDSRzF4.png

I've been playing around with jitsi (https://jitsi.org/) and have been impressed. I may play around with deploying their server on aws this weekend (via this docker, most likely: https://github.com/jitsi/docker-jitsi-meet)

Correct link: https://github.com/jitsi/docker-jitsi-meet

The docker setup instructions at least seems safe in that regard: https://github.com/jitsi/docker-jitsi-meet#design-considerat...

Well, it is indeed easy to self-host it if you happen to already have a https-reachable server running Debian on a common CPU instruction set. Which I had, yet for maintenance reasons a container-based solution had my preference: https://github.com/jitsi/docker-jitsi-meet

Do you know the oss https://jitsi.org/jitsi-meet/ They also have docker containers: https://github.com/jitsi/docker-jitsi-meet

If you use it via docker compose there is nothing hard to self host. I literally tried this out within minutes. A few more minutes to put it on the normal port with a real certificate. https://github.com/jitsi/docker-jitsi-meet

For those of you who need to try it out real quick : Jitsi Docker : https://github.com/jitsi/docker-jitsi-meet