Miss Rose bot

See the Miss Rose bot for a full understanding of its features. A few limited features from Rose are used for the Api3 group. Rose is not used by the Api3 Administrators or Logging groups.

Use the /connect command to tell Miss Rose which group to make changes for. Use the appropriate chat identifier from the config.json file.

Important

It is important to open a chat using the Miss Rose bot to make changes to her behavior for a main groups (Api3 or Curt). Do not make changes directly within a group to avoid message chatter.

# This will connect Rose to the Api3 main group
/connect <see-config.json>

The following sections show the settings have been applied to Miss Rose for the main group.

https://missrose.org/docs/greetings/

Welcome message and captcha

Rose is not used to verify users are human or to greet them. Turning off the /welcome message also disable the /captcha. The current captcha settings will remain intact should the welcome message be turned back on.

/welcome off

# To see the status of the welcome message
/welcome

I am currently welcoming users: false
...

Cleaning commands

Every time someone uses a command in the group, it stays there - making it possible for people to accidentally tap the command and re-send it. This can be frustrating, and lead to unwanted spam.

/cleancommand all

# To see the current status
/cleancommand

The following command types currently get cleaned in Curt:
- all
- admin
- user
- other

https://missrose.org/docs/cleaning/clean-command/

Cleaning service messages

Telegram often sends service messages such as "X joined the chat", "X left the chat", "X pinned a message", or "X joined the voice chat". These typically show as little grey icons in the chat.

/cleanservice on

# To see the current status
/cleanservice

The following service messages are currently being deleted in Curt:
- all
- join
- leave
- other
- photo
- pin
- title
- videochat

https://missrose.org/docs/cleaning/clean-service/#enabling-cleanservice

Command Disabling

While Rose has tons of commands, you might not want all of them available to your users. Leaving every command available may lead to a lot of spam and abuse of the bot, depending on how well-behaved your users are of course! This is where command disabling come in. With command disabling, you can completely disable certain commands from all your non-admin users.

Not all commands can be disabled. Checking those that can be:

/disableable

https://missrose.org/docs/moderation/disabling/

Disable commands for user

/disable all

Disable all commands listed in the /disableable for non-admin members. For those admin commands that cannot disabled, Miss Rose will not allow non-admins to run them. But a message will appear in the group: "You need to be an admin to do this."

Disable commands for admins

/disableadmin on

# To see the current status
/disableadmin

Disabled commands in Curt cannot be used by admins.

https://missrose.org/docs/moderation/disabling/#disabling-commands-for-admins-too

Deleting Disabled Commands

When you disable a command, a user can still send the command in your chat. However, instead of responding, Rose will simply ignore the command. This is where deleting disabled commands come in. With this option, Rose will still ignore any disabled commands, but she will also delete any disabled commands sent by users.

/disabledel on

# The status of this command cannot be checked, just changed.

https://missrose.org/docs/moderation/disabling/#deleting-disabled-commands