The exploit is not known in this case. The claim that it was password protected seems like an unverified statement. No pg_hba.conf content provided, this docker must have a very open default config for postgres.
`Ofcourse I password protected it, but seeing as it was meant to be temporary, I didn't dive into securing it properly.`
its really hard to ignore the persons character, but not addressing the argument (and instead talking about the persons character) is a logical fallacy.
I haven't tried this at scale, but was pleased with 6 participants on my $200 r710 hardware with 10megabits upload connection service. Memory usage is minimal, couple GB tops. Not running high-res, but was good enough. I mean they develop this and make it freely available for self-host, I'm pleased.
I have an old R710 with 24 cores and 32GB I got on ebay for $200 in my dining room with 10mbits upload/100 download and it works great. bought my .me domain for $5. It's a wonderful time to be alive.
I’ve run 10-12 users with video and desktop screen sharing on a 6 core azure vm with between 20-30% cpu load with spikes to 46%. It also depends a bit on the adaptive bit rate. Image quality of FaceTime is higher than Jitsi.
Jitsi uses about 5.5Mbps per connected Chrome user. This math doesn't line up, but if Jitsi isn't transporting the 720p video 10Mbps might work for 6 users.
1:1 video uses P2P and doesn't require video going through the Jitsi bridge.
Tbf, the bitrate depends entirely on the res constraints you've specified. We see 1Mbps when requesting 854x480, which seems to be quite a reasonable resolution when on a multiway conference.
It not my experience at all. In fact it was the easiest install I have ever done. It knew I was using nginx as a reverse proxy and inserted itself correctly as a subdomain. The only issue I had was webmin was running on port 10000 which created a conflict because it also wanted to bind to 10000.
After reading your message, I tried installing it on archlinux, and here we are 3 hours later and I still didnt figure out to make it work, so I'm sadly giving up
You can export to whatever you like. In our imagination, data versioning would sit upstream of production just like source code versioning. You take the data out and do what you need with it in a "compile" step.
`Ofcourse I password protected it, but seeing as it was meant to be temporary, I didn't dive into securing it properly.`