cadence/out-of-your-element
cadence
/
out-of-your-element
2
6
Fork 1
Code Issues 13 Pull Requests Releases 10 Activity

registration.yaml invite should also apply retroactively #37

New Issue
Open
opened 2024-02-18 02:39:02 +00:00 by cadence · 0 comments
cadence commented 2024-02-18 02:39:02 +00:00
Owner
Copy Link

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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
alt-host
v2.1
v2.0
v1.5.1
v1.5
v1.4
v1.3
v1.2
v1.1.1
v1.1
v1.0
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
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.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?