Shawn Chin

There is now a prosody plugin in jitsi-contrib to autostart lobby for all rooms -- https://github.com/shawnchin/prosody-plugins/tree/main/lobby_autostart As mentioned in the discussion above, this is only practical if you have some...

> Is there an "default password for room" feature I am unaware about? I don't think there is official support for that, but there are several posts in community with...

AFAIK, there is not such env var so should not influence anything.

sorry. force pushed a small fix to handle missing import.

I've been testing this further, in particular mod_persistent_lobby, and found an edge case where it doesn't work -- when there are existing moderators in the room and we programmatically trigger...

yes. It works when done in the UI. I think the problem here is that we are only triggering the broadcast to existing moderators on 'muc-config-submitted' event ([ref](https://github.com/jitsi/jitsi-meet/blob/fb2cfaa204734a68e376d9a53c567eec4a0d2c74/resources/prosody-plugins/mod_muc_lobby_rooms.lua#L325)). When done...

I will explore some options :) Notifications for automated lobby will be a bit different because it doesn't have a real actor, and I don't want to break current functionality...

If I'm understanding correctly, it looks like we also need to worry about affiliations of all the existing members in the room before `room:set_members_only()` -- the call will [kick out...

Thanks. I've handle the case for setting everyone to member. Now just need work out how to properly handle muc#roomconfig form submission, and notification to existing moderators. Work in progress...

I see. I will try that. But perhaps as a separate PR at some point? That use case does not affect reservations module or standard case where moderators trigger lobby....