I understand that now, with the code of ColloCall, we’re able to set the environment variables of a Greenlight container to define, for the whole container three key variables: max #participants, #rooms per host and #duration of a session. That’s a great step forward as these are key variables to define service levels and share somehow the costs of running the services. Good for now. But what if these variables could be set on a user role level inside Greenlight? That way with one instance we could run users with various service levels inside the same container and thus enable them to share rooms more easily, and on the same domain name. Ultimately that could lead to a simpler and better user experience.
I’d imagine this process:
- user signs up, confirms a contribution related to a certain service level, and gets immediate access as a “free” user
- the user onboarding team (possibly decentralised through different collectives) validates the account, and the user account gets upgraded to the desired service level
Note that the users in the this process can all get access to the same domain name, where they can create and share rooms between each other. This is a powerful feature that in the current service level proposal we can’t really use (yet).
Maybe it would be good to study the discussions inside the the BBB community for this purpose and see how much effort it would cost to enhance Greenlight for this purpose? When we can obtain funds for developing this, wouldn’t it be a valuable contribution?