Live data from Hacker News

Jitsi Meet – Improving Scale and Media Quality with Cascading SFUs (2018)

webrtchacks.com

111–115 of 115 posts

Re: Jitsi Meet – Improving Scale and Media Quality with Cascading SFUs (2018)

#111
post #40

Jitsi-meet is very easy to install and to setup. "apt install jitsi-meet" and you have almost all done. The documentation is very good. It works great and it is super userfriendly. You have no excuses.

FYI -- I tried this in a fresh Ubuntu 18.04 LXC container and it failed spectacularly.

There's a weird interaction between the NOFILE security limit (`ulimit -n`), Java 8, and Linux-based containers (noted on both LXC and Docker). If NOFILE is too high, Java 8 will paradoxically run out of memory as it tries to allocate some huge number of file descriptors. That took a while to figure out, since generally when you get an error about exhaustion of file descriptors, you expect the opposite!

So just set a lower security limit, right? It doesn't seem to work, I'm assuming because something in the Jitsi install process decides it needs to set them really high for the install session. I haven't debugged what component specifically is doing this yet. This results in the install scripts crashing when the installer tries to initialize the Java CA store.

In theory one could wait for that crash, reset the file limit, and then resume the install process. This works to a certain point, but every time I tried it, the crash in the CA store initialization would leave the dpkg database in a badly broken state that `apt-get --fix-broken install`, `aptitude`, and some manual dpkg futzing wasn't able to fix in the course of the 3-ish hours I spent working on it (complains on libc6-linux-dev package install that /usr/include/linux/something-something.dpkg-new doesn't exist; that folder structure isn't present on disk).

Technically Jitsi is set up by this point because the crash occurs as part of the certbot bootstrap, but I was working on getting Janus to work anyway and just tried out jitsi-meet because they had an autoinstaller that would set up Prosody, JVB, and all that good stuff anyway, so it wasn't really worth plugging through the rest of the way or dealing with the broken half-installed Jitsi, especially since there are many warnings about how you must configure the SSL bits properly in the install documentation.

But it'd be great if someone wanted to fix all that and make my life easier. :)

Re: Jitsi Meet – Improving Scale and Media Quality with Cascading SFUs (2018)

#112
post #40

Jitsi-meet is very easy to install and to setup. "apt install jitsi-meet" and you have almost all done. The documentation is very good. It works great and it is super userfriendly. You have no excuses.

> You have no excuses. Billions of users who aren't using linux distros with aptitude have an excuse. This isn't remotely close to the "just works" that you need to get wide adoption.

Yet it is probably the easiest and most "just works" solution to self host conferencing.

Of course if you don't selfhost anything it's not option for you.

Re: Jitsi Meet – Improving Scale and Media Quality with Cascading SFUs (2018)

#113

Earlier quoted context omitted.

riot.im hosts its own Jitsi instance which is built into the UI, so hitting the call button in a room will spawn an embedded Jitsi call in the room. Recently we added the option for people to use their own self hosted Jitsi instances, if they prefer. (1:1 calls at the moment are normal WebRTC, directly over Matrix)

I might be breaking the rules, but can you point me towards any information about how to integrate my existing self-hosted jitsi server into my self-hosted matrix install? Finding this seems elusive.

I tried and i don't think its easily possible.

Re: Jitsi Meet – Improving Scale and Media Quality with Cascading SFUs (2018)

#114

Earlier quoted context omitted.

> Obviously as we stopped using Zoom we have to manually upload all our personal data to Facebook now. I feel like there is a joke that's going over my head or I simply don't understand. Why you have to manually signup/login/auth/whatever with Facebook because you're using Jitsi now, especially on your own host?

The joke is that zoom was found to be sending user info to Facebook apis.

I missed that story so it went completely over my head. Now I could read about it, thanks!

Re: Jitsi Meet – Improving Scale and Media Quality with Cascading SFUs (2018)

#115

Earlier quoted context omitted.

Does this explain why I get poor Jitsi experience on my laptop and better using the Android app on my phone?? I suspect you are hitting on the exact issue I'm having. I have a Thinkpad with just the Intel 5500 GPU, nothing superb. So, how do I figure out if at least that is being used or not?

Windows Task Manager will show you GPU utilization on the Performance tab. Start Task Manager, then start your browser and see if there is an uptick. Then start a meeting to see if there is another one. There probably won't be. Then, disable the software rendering override in your browser: (Firefox: https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drive... ) (Chrome: https://superuser.com/questions/836832/how-c…

Why would you assume I'm on Windows?

I'm on GNU/Linux here.

But anyway, yes, I see specifically an uptick in the CPU dramatically with meetings, distinct from other browsing.

Post reply on HN