Keep track of what rooms the bot is in, and what users are in them

projectmoon commented

2020-10-18 21:00:03 +00:00

Owner

This is necessary foundational work for managing the bot's services in a private chat (direct message) instead of spamming commands out in the open. As most commands are planned to be per-room, giving commands in a DM need to be contextually aware of a room, either by giving a room ID/number or setting the room and having all commands afterward operate on that room.

Checklist:

Prevent duplicate event processing due to the way Matrix SDK retrieves events when joining a room.
When a user joins a room, and record the user in the rooms namespace in the database.
When a user leaves the room, remove the user from the room list.
When the bot joins a room, add all users in the room to the database.
When the bot joins a room, add the room name/ID to a room info struct/tree.
When the bot leaves a room, wipe out all information about the room from the database.
On startup, sync room member lists as an async task. Update member list for every room the bot is in.

The bot should always exclude itself from member lists. Because direct messages are rooms, we might also want to ignore direct message rooms. This can be done with Matrix SDK.

This is necessary foundational work for managing the bot's services in a private chat (direct message) instead of spamming commands out in the open. As most commands are planned to be per-room, giving commands in a DM need to be contextually aware of a room, either by giving a room ID/number or setting the room and having all commands afterward operate on that room. Checklist: - [X] Prevent duplicate event processing due to the way Matrix SDK retrieves events when joining a room. - [X] When a user joins a room, and record the user in the rooms namespace in the database. - [X] When a user leaves the room, remove the user from the room list. - [ ] When the bot joins a room, add all users in the room to the database. - [ ] When the bot joins a room, add the room name/ID to a room info struct/tree. - [X] When the bot leaves a room, wipe out all information about the room from the database. - [ ] On startup, sync room member lists as an async task. Update member list for every room the bot is in. The bot should always exclude itself from member lists. Because direct messages are rooms, we might also want to ignore direct message rooms. This can be done with [Matrix SDK](https://github.com/matrix-org/matrix-rust-sdk/commit/883183324f7c8a0a0afc92b8c906ab51be9a12b7).

projectmoon referenced this issue

2020-11-09 21:25:21 +00:00

Room State Management #44

projectmoon commented

2020-11-10 20:40:53 +00:00

Author

Owner

These will be implemented by #44:

Prevent duplicate event processing due to the way Matrix SDK retrieves events when joining a room.
When a user joins a room, and record the user in the rooms namespace in the database.
When a user leaves the room, remove the user from the room list.
When the bot joins a room, add all users in the room to the database.
When the bot leaves a room, wipe out all information about the room from the database.

This leaves these two remaining to be implemented in a later PR:

When the bot joins a room, add the room name/ID to a room info struct/tree.
On startup, sync room member lists as an async task. Update member list for every room the bot is in.

These will be implemented by #44: - Prevent duplicate event processing due to the way Matrix SDK retrieves events when joining a room. - When a user joins a room, and record the user in the rooms namespace in the database. - When a user leaves the room, remove the user from the room list. - When the bot joins a room, add all users in the room to the database. - When the bot leaves a room, wipe out all information about the room from the database. This leaves these two remaining to be implemented in a later PR: - When the bot joins a room, add the room name/ID to a room info struct/tree. - On startup, sync room member lists as an async task. Update member list for every room the bot is in.

projectmoon referenced this issue from a commit

2021-05-24 21:46:30 +00:00

Remove room state mgmt; let matrix SDK do it on-demand instead.

projectmoon commented

2021-05-24 22:25:00 +00:00

Author

Owner

This issue is closed by actually removing all of the code implemented in #44, because the Matrix SDK can do this for us on demand with locally cached information.

projectmoon closed this issue

2021-05-25 14:02:29 +00:00

Keep track of what rooms the bot is in, and what users are in them #20