gorb/specifications
5
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Implement Permissions #2

New issue
Open
opened 2025-07-02 15:41:47 +00:00 by twig · 0 comments
twig commented 2025-07-02 15:41:47 +00:00
Owner
Copy link

We need a proper permission system, currently we've implemented these:

SendMessage
CreateChannel
DeleteChannel
ManageChannel
CreateRole
DeleteRole
ManageRole
CreateInvite
ManageInvite
ManageServer
ManageMember

I think the permissions such as CreateRole and DeleteRole shouldn't exist, as letting users create stuff without being able to clean up after themselves.

Due to technical reasons, I think it's a really good idea to limit the system to 64 permissions, so they can be stored in a single integer.

I also think we should add a CreateCustomInvite permission, which would allow users to write a custom string for the invite link, since "normal" users shouldn't be able to "call dibs" on cool invite strings for the instance.

In the future, we also need ManageMessage, to pin and delete messages. Change and Manage Nickname. Kick, Ban, and Timeout Member. AttatchFile. AddReaction. UseCommand.

But my current desired permission list would be as follows:

SendMessage
ManageChannel
ManageRole
CreateInvite
CreateCustomInvite
ManageInvite
ManageServer
ManageMember

But please reply with any thoughts or opinions!

We need a proper permission system, currently we've implemented these: SendMessage CreateChannel DeleteChannel ManageChannel CreateRole DeleteRole ManageRole CreateInvite ManageInvite ManageServer ManageMember I think the permissions such as CreateRole and DeleteRole shouldn't exist, as letting users create stuff without being able to clean up after themselves. Due to technical reasons, I think it's a really good idea to limit the system to 64 permissions, so they can be stored in a single integer. I also think we should add a CreateCustomInvite permission, which would allow users to write a custom string for the invite link, since "normal" users shouldn't be able to "call dibs" on cool invite strings for the instance. In the future, we also need ManageMessage, to pin and delete messages. Change and Manage Nickname. Kick, Ban, and Timeout Member. AttatchFile. AddReaction. UseCommand. But my current desired permission list would be as follows: SendMessage ManageChannel ManageRole CreateInvite CreateCustomInvite ManageInvite ManageServer ManageMember But please reply with any thoughts or opinions!
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
backend
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: gorb/specifications#2
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?