|
|
|
@ -76,10 +76,10 @@ of the specified servers until either it is able to join or gets a `403 M_FORBID
|
|
|
|
|
When rejecting an invite, the server should also do the same as above but for the `/make_leave` and `/send_leave`
|
|
|
|
|
endpoints, iterating over the servers until it either is able to leave or gets a `403 M_FORBIDDEN` response.
|
|
|
|
|
|
|
|
|
|
In the case where multiple users on the same server have recieved invites to the same room over federation, servers
|
|
|
|
|
In the case where multiple users on the same server have received invites to the same room over federation, servers
|
|
|
|
|
in the most recent invite should be attempted first, and should work through invities in reverse chronological order,
|
|
|
|
|
attempting the servers specified in each as explained above. Servers should only be attempted on their most recent
|
|
|
|
|
appearence.
|
|
|
|
|
appearance.
|
|
|
|
|
|
|
|
|
|
## Potential issues
|
|
|
|
|
|
|
|
|
@ -93,7 +93,7 @@ is actually in the room.
|
|
|
|
|
## Security considerations
|
|
|
|
|
|
|
|
|
|
The invited server now knows some of the servers that are in the room without having to join, which could be
|
|
|
|
|
undesireable if the room is private.
|
|
|
|
|
undesirable if the room is private.
|
|
|
|
|
|
|
|
|
|
## Unstable prefix
|
|
|
|
|
|
|
|
|
|