You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the evolving landscape of digital group interactions, there's a pressing need for a more flexible, secure, and inclusive group management infrastructure. Traditional models often impose rigid rules that can stifle group dynamics and hinder user engagement.
When a group is created in Bandada, the admins must follow the current rules set by the Bandada API implementation. For instance, if a user is removed from a credential group, they cannot rejoin it or, if a user wants to leave an off-chain group, the admin must remove them as they cannot do so independently. There are situations where this feature is okay, while in others it can be restrictive.
My proposal seeks to introduce a groundbreaking settings system that empowers group creators with the ability to select from a set of group management rules, avoiding Bandada being a decision making point. For example, an admin can check rules at group creation time like:
Credential Group ...
[ ] Do you want to enable users to leave the group on their own?
[x] Do you want to allow the admin to remove users?
[ ] Do you want to permit users who have been removed by the admin to attempt to rejoin the group?
This can have it has its limitations, and implementing all this logic on-chain would be complex. Overall, the solution has many positive points imho. Therefore, we need to discuss the trade-off between on-chain and off-chain implementation. Any feedback is more than appreciated.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In the evolving landscape of digital group interactions, there's a pressing need for a more flexible, secure, and inclusive group management infrastructure. Traditional models often impose rigid rules that can stifle group dynamics and hinder user engagement.
When a group is created in Bandada, the admins must follow the current rules set by the Bandada API implementation. For instance, if a user is removed from a credential group, they cannot rejoin it or, if a user wants to leave an off-chain group, the admin must remove them as they cannot do so independently. There are situations where this feature is okay, while in others it can be restrictive.
My proposal seeks to introduce a groundbreaking settings system that empowers group creators with the ability to select from a set of group management rules, avoiding Bandada being a decision making point. For example, an admin can check rules at group creation time like:
This can have it has its limitations, and implementing all this logic on-chain would be complex. Overall, the solution has many positive points imho. Therefore, we need to discuss the trade-off between on-chain and off-chain implementation. Any feedback is more than appreciated.
Context #342 (comment)
Beta Was this translation helpful? Give feedback.
All reactions