In our Jitsi Meet instance we have added a new config value specific to our instance. This value can be changed while the application is running and is essentially used to lock the meeting when users do not set their own unique password.
Everything is working with the new config file when we refresh the page, the problem I am running into is when the config value is changed when a user removes their password, this leads to the front-end showing as though the config value was set to the old value, not the new one. However, when i refresh the page, everything works as expected.
Based on this, a simple (and potential) solution is to refresh everyone’s instance whenever the password is changed. This would not be as user friendly and I would need to probably have some sort of short delay on each person’s screen to avoid them thinking something is going wrong with our meeting platform (something like “The meeting password has been changed. This meeting will refresh in 4 seconds…”
However, even with that as a potential solution, I am still curious if there are any other options. Is there a way to update the interface_config values that are used in everyone’s instance without refreshing them?
Thank you for any advice you can give regarding this!