On Decentralisation and The Online Meeting Cooperative

[decentral1se]

Thanks for laying that out @wouter

@chris

@wouter

how will Scalite be able to connect to recordings on different servers?

Exactly, there would have to be a central file server and a central PostgreSQL database, these things won’t work well unless we have some really clever solution, plus how would people pick which continent they want their conference to be hosted on?

Tough, yep. Each Greenlight front-end can only see the rooms/recordings that it makes, which is tied into the index database of scalalite and the shared storage volume of the underyling BBB instances. I guess there would need to be some source code changes to allow for swapping out some of this stateful logic to allow for distributing rooms/recordings. It seem like the bbb-setup mailing list is the place to dig further…

@chris

I really think that for the beta stage separate BBB server instances (which might well be multiple severs themselves with a scalelite front end), for example es.meet.coop , ca.meet.coop , uk.meet.coop , nz.meet.coop , se.meet.coop , perhaps with a central SSO so people can open rooms on a server of their choosing, is the best we can realistically aim for.

I guess we’re leading towards a central LDAP server auth which Greenlight supports. Another option is that I see there is also functional but WIP () work for Greenlight supporting OpenID Connect. This could allow for something like a central Keycloak SSO which can be themed out of the box and administered through a web interface. I’ve also seen that Keycloak can plug-in existing LDAP providers for user federation.

EDIT: there was also talk of commonscloud / cc-onboarding · GitLab