summary refs log tree commit diff
path: root/synapse/rest/media/v1/preview_url_resource.py
diff options
context:
space:
mode:
authorAndrew Morgan <1342360+anoadragon453@users.noreply.github.com>2020-10-13 15:49:50 +0100
committerGitHub <noreply@github.com>2020-10-13 15:49:50 +0100
commit722e1c016a9fbb55264977f986af8e3ea23f0712 (patch)
treec8142715f7572d91ffe56eba5dd48dab93a0fc16 /synapse/rest/media/v1/preview_url_resource.py
parentAllow modules to create and send events into rooms (#8479) (diff)
downloadsynapse-722e1c016a9fbb55264977f986af8e3ea23f0712.tar.xz
"Freeze" a room when the last admin of that room leaves (#59)
If the last admin of a room departs, and thus the room no longer has any admins within it, we "freeze" the room. Freezing a room means that the power level required to do anything in the room (sending messages, inviting others etc) will require power level 100.

At the moment, an admin can come back and unfreeze the room manually. The plan is to eventually make unfreezing of the room automatic on admin rejoin, though that will be in a separate PR.

This *could* work in mainline, however if the admin who leaves is on a homeserver without this functionality, then the room isn't frozen. I imagine this would probably be pretty confusing to people. Part of this feature was allowing Synapse modules to send events, which has been implemented in mainline at  https://github.com/matrix-org/synapse/pull/8479, and cherry-picked to the `dinsic` fork in 62c7b10. The actual freezing logic has been implemented here in the RoomAccessRules module.
Diffstat (limited to 'synapse/rest/media/v1/preview_url_resource.py')
0 files changed, 0 insertions, 0 deletions