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
The matrix protocol specifies that clients (both the creator of a DM room and joiners) are in charge to flag the room as DM chat.
This is being done in two places but using the same mechanism: account_data (event m.direct).
On rooms' creation we already update the account data automatically (done in Rust).
This issue is about updating m.direct when accepting an invitation for a DM chat.
Behaviour
When accepting an invitation the user looks inside his invite (an event of type m.room.member) and check under the path content.is_direct if the flag is set to true. If yes, he has to register the room id in his own account_data inside m.direct just after he joins the room.
The text was updated successfully, but these errors were encountered:
alfogrillo
changed the title
Update the account data event m.direct when receiving a new invite for a dm chat
Update the account data event m.direct after accepting an invite
Mar 20, 2023
The matrix protocol specifies that clients (both the creator of a DM room and joiners) are in charge to flag the room as DM chat.
This is being done in two places but using the same mechanism:
account_data
(eventm.direct
).On rooms' creation we already update the account data automatically (done in Rust).
This issue is about updating
m.direct
when accepting an invitation for a DM chat.Behaviour
When accepting an invitation the user looks inside his invite (an event of type
m.room.member
) and check under the pathcontent.is_direct
if the flag is set to true. If yes, he has to register the room id in his ownaccount_data
insidem.direct
just after he joins the room.The text was updated successfully, but these errors were encountered: