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
When deactivating a user, synapse goes through a cleanup process which includes steps to remove the user from the federation. This includes parting all joined rooms and rejecting pending invites:
MSC2403 introduced knocking. Knocks similarly to invites linger until either retracted or approved/denied by another actor. Hence, similar to pending invites being shown in the room member list, knocks would usually also be shown to at least those room members with sufficient power level to manage them.
The synapse cleanup routine should also take care of pending knocks, setting them to leave instead.
This could be done by replacing the call to get_rooms_for_user() with a cloned one that does not only consider JOIN but also KNOCK
Description
When deactivating a user, synapse goes through a cleanup process which includes steps to remove the user from the federation. This includes parting all joined rooms and rejecting pending invites:
synapse/synapse/handlers/deactivate_account.py
Lines 167 to 173 in 232adfb
MSC2403 introduced knocking. Knocks similarly to invites linger until either retracted or approved/denied by another actor. Hence, similar to pending invites being shown in the room member list, knocks would usually also be shown to at least those room members with sufficient power level to manage them.
The synapse cleanup routine should also take care of pending knocks, setting them to leave instead.
This could be done by replacing the call to
get_rooms_for_user()
with a cloned one that does not only considerJOIN
but alsoKNOCK
synapse/synapse/storage/databases/main/roommember.py
Line 690 in 232adfb
or a new function similar to
synapse/synapse/handlers/deactivate_account.py
Line 197 in 232adfb
but I could not find an existing method to list a user's pending knocks yet, so that would need to also be added.
Steps to reproduce
Homeserver
another
Synapse Version
1.93
Installation Method
Docker (matrixdotorg/synapse)
Database
psql, single, not ported, probably yes
Workers
Single process
Platform
k8s rancher
Configuration
Relevant log output
Anything else that would be useful to know?
No response
The text was updated successfully, but these errors were encountered: