denexapp / cute-bot Goto Github PK

Check that the bot has admin rights in the conversation on command. Send an error message if the bot doesn't have them.

• vk-ts: Add error handling
• vk-ts: Throw exception on error 917 of messages.getConversationMembers
• Add a flag to chat settings. This flag shows if the message about rights was shown
• Catch the exception and send a message saying that bot needs permissions in order to work (if it's a command or the flag is false)

Messages with commands for the bot looks like noise in a chat. It would be good to add a mode to remove such messages.

Users may interact with non-admin commands now. That's not how it should be by default, but this behavior may be useful.

• Add a mode commands that allow or forbid users to interact with the bot
• Ignore commands sent by non-admins if the mode is off

It requires to have a connected callback server to a conversation to enable or disable callback mode. It's not necessary to check for a callback server to disable a mode.

Disable this check

Send when the bot joins a conversation. Mention the /help command

Sometimes you need to send a predefined text several times. It would be easier to add a way to save these messages and ask bot to send them with a short command.

• Add a command to add template
• Add a command to edit existing template
• Add a command to show a list of existing templates
• Add a command to remove existing templates
• Add a command to send existing template
• Add a shorthand to the command that sends existing template
• Add a way to save templates to the database

Some bad people may spam to the bot using other bots. Even without it, it's not an expected behavior when the bot reacts to a bot.

• Ignore messages from communities

It's not clear how to set up callback server now. Need to add an instruction.

• cute-bot-callback: Add readme with Deploy on Vercel button
• Cute Bot VK: write an article about callback server
• Add environment variable with URL of the article
• Add the link to the article to /callbackAdd and /callbackConnect error messages

When the bot gets kicked form a chat, settings that belong to this chat stay. These settings should be removed automatically

If there are multiple bots in a conversation, a message that command is unknown will be triggered even if it's a valid command for another bot.

• Add actionless modes
• Replace 'enableUserCommands' and 'disableUserCommands' with a new actionless mode 'ignoreUsers'
• Add new mode called 'ignoreUnknownCommands'

Since the bot is used by some chats right now, it will be a good time to start to use 2 environments: dev and production.

• Set up preview environment on Vercel
• Create a group on vk.com
• Create a database in Fauna

Command add is used to add a callback server. If there's an already connected callback server, it replies with an error. It says, to add the new server you should remove the old one first. But this message feels weird if a user tries to add the same callback server.

Add specific error message if a user adds a callback server with the same URL

Sometimes handling a command may take a while. It will be a good idea to send "Cute Bot is typing" status when handling of command starts.

• Add the corresponding method to the vk-ts package
• Add "sends message" flag to commands and modes
• Add a global queue for messages: a counter and two methods: imGonnaSend() and send()
• Send "typing" status on errors, commands, and modes

/help text looks ugly. It's hard to distinguish where a previous command ends and the next starts.

Prefixing every command with an emoji will help to solve that

Current messages are awful.

Bot's messages should look like it's talking with you, like a person. Messages shouldn't look like some system notifications.

Rewrite them to make them look more human-ish

Add a mode that removes messages with Russian swear words.

• Add russian-bad-words package
• Add mode
• Add function that detects bad words in the message

There are several cases when a callback server gets disconnected from a conversation. In these cases, the callback modes list should be cleared. A list of disabled modes should be also shown

• Clear the list of callback modes in a conversation when the callback server disconnects
• Add i18n for lists
• List active callback modes that can't apply their effect because there's no callback server
• List disconnected callback modes on /callbackDisconnect
• List disconnected callback modes on /callbackRemove
• List disconnected callback modes on /callbackSecretReset