392021-02-09 04:31:24ClintonEbadilink to debian postinst scripts, contains some clues as to why the puppet module is totally broken382021-02-09 03:58:48ClintonEbadineed to update nginx config, turnserver372021-02-05 19:13:44ClintonEbadisome leads on breakout room support362021-01-21 01:13:11ClintonEbadidoesn't look like we have to set the unencrypted auth option352021-01-21 01:10:42ClintonEbadiactually no tokens, just have to actually load the modules into the prosody vhost and whatnot342021-01-21 00:51:12ClintonEbadiusing sasl requires using tokens or something332020-12-08 05:09:02ClintonEbadienablelayersuspension is very important322020-12-08 04:53:57ClintonEbadilink to pwa-worker.js that seems to work312020-12-08 04:40:27ClintonEbadifinding some fun bits while tightening up a default install302020-12-07 18:29:57ClintonEbadifound an entire document dedicated to self-hosting jitsi meet, looked solid on first glance292020-12-07 01:02:36ClintonEbadinote to self to check if the puppet module is using the deprecated nginx vhost style282020-12-02 04:59:29ClintonEbadiauth domain is wonky272020-12-02 03:48:15ClintonEbadiwe have a combined pem, the puppet module doesn't like that262020-09-02 19:32:06ClintonEbadianother thread252020-09-02 19:29:46ClintonEbadifound a couple of threads discussing performance tuning242020-08-24 22:31:59ClintonEbadi232020-08-24 21:22:50ClintonEbadimight be worth trying jitsi meet with ejabberd222020-08-24 05:38:19ClintonEbadibig blue button as a possible alternative212020-08-22 20:59:14ClintonEbadialso need to set jicofo heap limit202020-08-22 20:54:54ClintonEbadimake sure we tune ram allocation192020-08-14 18:52:42ClintonEbadiprejoinPageEnabled looks useful182020-08-13 04:53:04ClintonEbadiedumeet might not be worth evaluating after all172020-08-13 04:50:39ClintonEbadi162020-08-13 04:49:14ClintonEbadiedumeet may also be worth evaluating152020-08-12 20:49:59ClintonEbadiwe need to set fileRecordingsEnabled: false142020-08-10 22:34:42ClintonEbadisome initial test data, open issues to explore132020-08-10 22:32:55ClintonEbadiheading level fix122020-08-10 21:50:36ClintonEbadicouldn't get branding url to work112020-08-10 21:32:58ClintonEbadifew interface settings we might want to tweak in addition to the ones the fsf tweaks102020-08-10 21:21:40ClintonEbadi92020-08-10 21:21:24ClintonEbadithere's some apache support, maybe82020-08-10 21:15:10ClintonEbadietherpad might be nice to have72020-08-10 21:10:57ClintonEbadiopen question about youtube62020-08-10 20:44:49ClintonEbadisome config settings we probably want to change52020-08-10 20:28:31ClintonEbadisome bits from the fsf config we probably want42020-08-10 03:45:12ClintonEbadi32020-08-10 03:01:32ClintonEbadisecuring the domain is useful22020-08-10 02:55:59ClintonEbadi12020-08-10 02:41:24ClintonEbaditrying out a jitsi meet installNotes on setting up Jitsi Meet on a personal server. Main thing is to note what we'd need to do to get this set up on an hcoop server

Followed the script and got a working install. We'll need to set config to provide our own cert jitsi-meet needs nginx out of the box /etc/nginx/sites-available/sites-available/meet.unknownlamer.org.conf Has its own xmpp server, prosidy (I think in theory we could integrate the videobridge with jabber but in practice probably not worth it at our scale) Working config out of the box, if we accept having to run this on a dedicated server.

The puppet modules has a few rough edges that we should fix and contribute upstream.

Since I installed meet.unknownlamer.org in July, jitsi has changed something with the vhost structure to avoid multiplexing: , make sure puppet is generating a config which doesn't do this Generated config does not work at all... review postinst for clues:

jitsimeet::config created an LE cert for "auth.${jitsimeet::jitsi_domain}", and using the hcoop wildcard cert we get a cert error, which does not occur on my test instance despite only having a cert for Subject: CN = meet.unknownlamer.org (no wildcard)

Forced to set jitsi_vhost_ssl_key and auth_vhost_ssl_key even when using combined PEM. Does not configure turnserver, which is needed for websockets Nginx config is stale, doesn't work with websockets (and needed config options aren't set), and the mobile client can't connect at all

Using on my personal DigitalOcean account. With a 2CPU/2G RAM setup, a 4 person conference used around 4Mbps and 10% CPU.

MIME type application/wasm wasm; was not set, appearing to cause chromium/firefox to just not use any of the wasm which seems bad for performance pwa-worker.js is missing in stable release packaging 1.0.4466-1 (Fixed in 4480)

Need to adapt to kerberos, will have to use SASL: (we have saslauthd in place for exim, so should be straightforward) There are some additional steps to auth against sasl: lua-cyrussasl must be installed from buster-backports on Debian 10. /etc/prosody/conf.avail/meet-test.hcoop.net.cfg.lua : /etc/sasl/xmpp.conf:

Can we limit room sizes?

review

We'll want to customize the css at least to match our usual color schema and insert the hcoop logo, and something like the blurb about the coop we include on git.hcoop.net Also, do we want to add librejs info? Not sure what the licensing on the youtube stuff is...

If we leave youtube support on, do we need to generate our own API keys, or is using the ones built into jitsi fine?

Thread on serving a large number of users Another thread on reducing cpu use Discussing hosting 500 person meetings (not feasible, but some advice there) Jitsi Club Self-Hosting Tuning Guide worth a review Recommends disabling currently speaking dot to lower client and server cpu use (fsf does this, I left it on in my testing instance): the detection apparently uses quite a bit of CPU. Further suggested tweaks to reduce client cpu use:

fileRecordingsEnabled defaults to true, since we will not support dropbox integration and don't want local recordings, we should set this to false to hide the interface elements that don't work resolution: 720 is the default (so 720p) max resolution, which seems reasonable for video conferencing Jiti by defaults starts with the mic and camera of participants on. The FSF starts with participants muted. I think that would be a more reasonable, privacy respecting default? Alternatively, we could set prejoinPageEnabled which allows participants to set or disable their camera/mic and set their nickname before entering the room should we use our own STUN server instead of the default provided by jitsi?: Instead of patching internal data, maybe we could just have a static json file on hcoop.net and use this to override logos? (My attempt to get this work on my local install didn't work, the react frontend should be making a request to brandingDataUrl but it never does for me) Maybe some bandwidth savings to be had? Update: yes, enableLayerSuspension: true is essential, it's not clear why it is not enabled by default at all. Misc

Override mobile download link to use F-Droid? Might want/need to customize these

Make sure we don't log more than the bare minimum.

VIDEOBRIDGE_MAX_MEMORY is converted to java -Xmx, make sure to tune appropriately for available ram on the server

JICOFO_MAX_MEMORY is converted to java -Xmx, make sure to tune appropriately for available ram on the server

Etherpad integration not sure how complete this is, but could be useful Packages come with an example apache config /usr/share/jitsi-meet-web-config/jitsi-meet.example-apache. Looks like all directives would work with domtool. it appears possible to use ejabberd instead of prosody if we want to integrate this with existing infrastructure there are several addon components that add break out room support

promises better performance by using VP9 instead of VP8 (40% reduced bandwidth). Advantage might be negated soon: Jitsi Meet has VP9 support actively under development. according to JackHill BigBlueButton may have more compatibility. It also integrates evernote and other nice things like breakout rooms, useful if we want to target organizations for membership.