I have been thinking about some changes we can do for the Discord. I’ll update this as we discuss them.
Note: I use the terminology “guild” here. This is how Discord refers to “servers” in its API, and is simply how I’m used to it. I prefer the distinction from the more usage-poluted word “server”.
Low impact changes
These are suggested to implement as soon as there is consensus to do so
- Strip all guild-level permissions from Team Roles, then give them to a master role (“Org Member”? Something else?) for all members of Amethyst to have
- De-hoist (hoist == separate from online list) the Team Roles, then hoist said master role
- Remove colours from Team Roles, as having distinct colours is more hassle than it’s worth. Does anyone memorize the teams by colour?
- Use said master role to lock the internal channels
- Remove TTS permissions for AtEveryone, as a preventative for someone being a nuisance
- Remove any permissions that AtEveryone has from all other roles, as everyone has the AtEveryone role and so such guild-level grants are redundant.
- Remove all permissions from the Admin role, save Administrator, since Administrator gives all permissions *
- Remove all per-channel overrides for the Admin role because they don’t do anything for roles with Administrator
- Enable message scanning for all messages, as a security precaution (will catch porn and viruses)
- Adjust the balance of View Channel, Send Messages, and Connect to Voice permissions as to respect that Send and Connect require View as a prerequisite
- Create text channel in Voice category for people to post among each other while in voice.
- This is because posts are usually with context that originates in voice, and so would be confusing at best, disruptive at worst
Practical infrastructure changes
These changes provide a significant difference in how the Discord is structured and how it operates
- Review separation of Admin, Moderator, and normal Team Member permissions and privileges, and redistribute *
- Suggested changes: Separate rename Admin to Root, to make the naming more about permissions than hierarchy, give Root to all Board Members who ask for it, a separate role for Discord Management that members of the Community Team may have, then remove administrative permissions from Moderator, making it a true moderator role, not an admin role.
- Implement a bot for channel opt-outs. Concept is simple, but it would require infrastructure. CD would be ideal, as to not need hosting privileges to update the bot.
- Alternative to Root permission: create a dedicated Amethyst user account which would be shared by Board Members, then transfer ownership to said account.
* Change requires the Guild Owner to make them (torkleyy)