You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you invite a user over federation and then change your mind (retract the invite, by setting their m.room.member membership to leave), there doesn't seem to be any mechanism to notify the invitee's server of that.
The result is that the invitee is left with a stale invite and when they try to redeem it, they get some generic error like 'Failed to make_join via any server' (Synapse example).
This is probably limited to the case where there aren't other users in the room on the same server as the invitee, otherwise the m.room.member event would be sent to the invitee's homeserver (by coincidence) and that probably leads to the right thing happening.
It seems there should be:
a Federation endpoint to notify about a retracted invite, but since that can't be guaranteed to be reliable, we also need...
an error code on make_join and send_join somehow informing the invitee that their invite has since been retracted, so clients can show an appropriate error message
If you invite a user over federation and then change your mind (retract the invite, by setting their
m.room.member
membership toleave
), there doesn't seem to be any mechanism to notify the invitee's server of that.The result is that the invitee is left with a stale invite and when they try to redeem it, they get some generic error like 'Failed to make_join via any server' (Synapse example).
This is probably limited to the case where there aren't other users in the room on the same server as the invitee, otherwise the
m.room.member
event would be sent to the invitee's homeserver (by coincidence) and that probably leads to the right thing happening.It seems there should be:
make_join
andsend_join
somehow informing the invitee that their invite has since been retracted, so clients can show an appropriate error messageVery similar in spirit to #146
The text was updated successfully, but these errors were encountered: