Do more validation during initialization #8

New issue

Open

opened 2025-09-01 11:00:27 +01:00 by Ghost · 0 comments

Ghost commented

2025-09-01 11:00:27 +01:00

(Migrated from codeberg.org)

We should do more validation during the initialization of the bot.

In particular, the bot should check:

Is the bot in the room? If not, write a message instructing that user must invite the bot. We can log the command the admin can do. i.e. /invite {}
If the bot is in the room, does it have permission to write messages? If not, log a warning.
Does it bot have permission to redact messages? If not, consider a fallback strategy and do an info log.
Does the bot have permission to notify everyone? Write an info log to let the admin know they can just grant the permission if they want the bot to do that.

We should do more validation during the initialization of the bot. In particular, the bot should check: * Is the bot in the room? If not, write a message instructing that user must invite the bot. We can log the command the admin can do. i.e. `/invite {}` * If the bot is in the room, does it have permission to write messages? If not, log a warning. * Does it bot have permission to redact messages? If not, consider a fallback strategy and do an info log. * Does the bot have permission to notify everyone? Write an info log to let the admin know they can just grant the permission if they want the bot to do that.

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

SethFalco/matrix-stream-alerts#8

No description provided.

Rows
Columns