janonym1

You are right, I only need the sip-commuicator.properties set up correctly for it to work as well. My bad! My approach would be something like: modifying the 10-config to keep...

done: https://github.com/jitsi/docker-jitsi-meet/pull/1343

I added a new var ENABLE_GCLOUD_TRANSCRIPTION but I am not sure, if my code at jigasi/rootfs/etc/services.d/jigasi/run seting the GCLOUD ENV for the key.json is working as intended

I also am not sure, if it would be better/nicer if we can chain the check for the GCLOUD creds in the 10-config: I wanted to AND together the following...

> Is there anything left to do? I would be happy to help. > > It would be very useful when this gets merged. Thanks I updated the requested changes...

I have posted also posted this in a different [issue88](https://github.com/ma1uta/ma1sd/issues/88) because I wasnt sure where this fits best. I have a similar issue with a similar setup. When I look...

I have a similar issue with a similar setup. When I look my at my account information (displayname, email) in my element profile, I get empty fields and the following...

To my knowledge, it does not since it is only one-way. You should look at https://gitlab.com/activism.international/matrix_ldap_registration_proxy or the [ansible-playbook-doc](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-playbook-matrix-ldap-registration-proxy.md)) if you want to forward registrated users into your LDAP

Communities was actually already removed with 1.61: https://github.com/matrix-org/synapse/blob/develop/docs/upgrade.md#removal-of-deprecated-communitygroups I maybe mistaken but I think, the communities (and spaces now) features was never really completely usable with ma1sd in the first...

Sure! We ran into similar problems with ma1sd and its syncing (but we still needed its search). So we run the script below regularly to sync user from ldap into...