bug: Sending a federated leave drops the reason field #768

Open
opened 2025-04-17 14:01:36 +00:00 by nex · 0 comments
Owner

According to s2s .13, the membership sent for a leave remotely can include a reason field in the membership object. However, this is only retained when leaving locally - when sending the leave via federation (i.e. when rejecting an invite to a room never seen before, such as a DM), the reason field is seemingly dropped while preparing the payload. This means that, for example, rejecting an invite with a reason omits the reason from the leave event sent.

According to [s2s .13](put_matrixfederationv2send_leaveroomideventid), the membership sent for a leave remotely can include a `reason` field in the membership object. However, this is only retained when leaving locally - when sending the leave via federation (i.e. when rejecting an invite to a room never seen before, such as a DM), the `reason` field is seemingly dropped while preparing the payload. This means that, for example, rejecting an invite with a reason omits the reason from the leave event sent.
nex added the
Bug
Matrix/Federation
Priority
Unknown
labels 2025-04-17 14:01:36 +00:00
Sign in to join this conversation.
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: continuwuation/continuwuity#768
No description provided.