-
-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rebuild permissions system. #104
Comments
Ideally, we could build it similar to how Discord inherits permissions so that there's not much of a learning curve. https://support.discord.com/hc/en-us/articles/206141927-How-is-the-permission-hierarchy-structured- Although, it would be worth adding role permission deny. |
Please do make sure that roles follow Hierarchy and override lower roles. |
Discord does not inherit permissions from the parent category. Revolt could depart from that and actually inherit from the parent category. Also to mention, it uses an "explicit allow wins" system which is inconvenient in a lot of respects. "Explicit deny wins" is better suited to express permissions for any serious use. |
Now closes #4 as of revoltchat/quark@d2e49a6. (This repo will be public once license is added.) |
Allows then denies, so explicit deny wins. This seems sane to me. After all, lockout is better than power out of control. |
Fix relevant issue revoltchat/revite#84 while we're at it. |
For #6 and #4.
Current hierarchy:
The text was updated successfully, but these errors were encountered: