registration.yaml `invite` should also apply retroactively #37

New issue

Closed

opened 2024-02-18 02:39:02 +00:00 by cadence · 1 comment

cadence commented

2024-02-18 02:39:02 +00:00

Owner

If OOYE is added to a server and it creates the rooms and then you realise you need to be invited to them, you're in a bit of a pickle. It should apply retroactively to all known rooms.

We can check whether to invite each Matrix user based on whether they have an m.room.member state key in the room.

To avoid checking every invite user in every room on startup, this will need some caching on which users have already been invited to which rooms from this feature.

If OOYE is added to a server and it creates the rooms and _then_ you realise you need to be invited to them, you're in a bit of a pickle. It should apply retroactively to all known rooms. We can check whether to invite each Matrix user based on whether they have an m.room.member state key in the room. To avoid checking every `invite` user in every room on startup, this will need some caching on which users have already been invited to which rooms from this feature.

cadence commented

2024-08-25 13:46:31 +00:00

Author

Owner

Power levels are now applied retroactively.

You can use the //invite command on Discord to get into the rooms if you miss the opportunity.

Power levels are now applied retroactively. You can use the `//invite` command on Discord to get into the rooms if you miss the opportunity.

cadence closed this issue

2024-08-25 13:46:32 +00:00

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: cadence/out-of-your-element#37

No description provided.

registration.yaml invite should also apply retroactively #37

registration.yaml `invite` should also apply retroactively #37