mirror of
https://github.com/the-draupnir-project/Draupnir.git
synced 2026-05-18 13:25:32 +00:00
Gnuxie
a086768b01
Support for room policies with hashed entity and `org.matrix.msc4204.takedown` recommendation in Synapse Story: https://github.com/the-draupnir-project/planning/issues/41 documentation: https://the-draupnir-project.github.io/draupnir-documentation/protections/room-takedown-protection This PR introduces room takedown functionality into Draupnir. A new `draupnir takedown` command is added similar to the ban command, but marks entities to be taken down. Because the content is illegal or intolerable. To begin with we only allow takedown of rooms. These takedown policies are sharable with policy lists just like normal bans. Draupnir responds to takedown policies on Synapse by calling the [room shutdown](https://element-hq.github.io/synapse/latest/admin_api/rooms.html#version-2-new-version) API with the options `block` and `purge`. The policies that are created by the takedown command are hashed, and this is in order to prevent the room id's being shared directly, and so that we do not create a directory of intolerable content. To be able to use the policies, draupnir therefore needs to be aware of all the rooms that the homeserver is participating in, in order to calculate their hashes and find matching policies, and then takedown the marked rooms. As part of this process, Draupnir has to "discover" the rooms your server is participating in. This is done via the [synapse-http-antispam](https://the-draupnir-project.github.io/draupnir-documentation/bot/synapse-http-antispam) recently added to draupnir. When draupnir discovers rooms, it will prompt the management room with a notification with some details of the title, room description, and creator. This functionality will be toggleable but will be strongly recommended for servers that have public registration