Discord cited privacy concerns in justifying the push for the new way to interact with Discord bots: Slash commands.
In light of the countless concerns presented and submitted by the Discord community regarding the push for slash commands, especially in terms of usability:
I would like to instead suggest changes to the implementation of "read permissions" granted to bots that may help resolve privacy issues while streamlining bot commands usage, building upon the already-existing and familiar "text commands", wherein:
- Discord will allow bots to read only text messages that start with a certain prefix or prefix + command. Text that do NOT contain known prefixes + commands will not be readable by bots.
- The scope, scenarios, and nature in which the Message Content Privileged Intent may be needed by bots will be reduced. Bots that perform functions such as, but not limited to server management and activity monitoring will still need the Privileged Intent to adequately perform.
- Discord will have to support a mechanism that handles the prefixes + text commands that each bot has, wherein defaults will be suggested or automatically set by the bot developers. This is in contrast to having the bots manage the prefixes themselves. This will also enable Discord to differentiate commands from conversations in text channels.
- The server administrators and moderators will be able to change prefixes for the bots through the server settings rather than through the bot.
- Should this be implemented, Discord must support a mechanism that may be described as an onboarding program or wizard tool that will enable the easy and painless transferring of existing configuration in bot prefixes, and also enable the submission of the commands lists so that bot operation in servers won't be disrupted.
Updated - 2022 Sept 06
Please sign in to leave a comment.