Open Ernest314 opened 2 years ago
Too much complexity, and most people don't have a use for tags. The ones who do can use /suggest
to get them added (#361).
Actually, there's a pretty simple way to do this which wouldn't introduce too much complexity. Simply save personal tags in a separate file (e.g. "tags-personal.txt"), and modify the subcommands as such:
list
: lists personal tags, followed by server tags. Even officers will only see their own personal tags (and not others').view
: everyone will have access to view server tags, and everyone will be able to view their own tags. Even officers will not be able to view other people's tags. Maybe force the response to be ephemeral for people with no rank?set
: this would always modify personal tags. Everyone (guest and above) will have permission to use this command.set-server
: only officers would have permission to use this subcommand.remove
: only allow officers to remove server tags (use special text on confirmation to indicate a server tag is being removed), but everyone can remove their own tags. Officers can also remove others' personal tags, but need to specify a user ID too (so someone would need to publicly post an offensive tag for officers to see the tag name). Use special warning text for removing others' personal tags, maybe encourage explaining the reason for removal to the user.set
, set-server
, and remove
should all have confirm interactables, and they should show a preview of the tag being modified.
Only check for tag name uniqueness between own personal tags and server tags; do NOT check for tag name uniqueness between own and others' personal tags.
Somehow indicate (maybe in the modal? There is already a warning there) that personal tags should not be considered private data.
Global tags should still only be editable by Officers, perhaps allow any Members to create personal tags? Decide if people should be able to view/use other members' personal tags.