This removes the need for synapse-http-antispam in order to reveal hashed literals for rooms. This is always available and by default runs a full scan every 30 minutes, or every time a policy changes. There is a configurable 5 minute cooldown between scans.
* Add the ability to customise the primary prefix for commands.
* Fix data structure error in config.yaml / harness.yaml
* Apply suggestions from code review
---------
Co-authored-by: Gnuxie <50846879+Gnuxie@users.noreply.github.com>
Extract out and depend upon @the-draupnir-project/mps-interface-adaptor
This is just a very simple PR to extract the contents of `src/command/interface-manager` and `src/capabilities/CommonRenderers.tsx` to a library that can be used by other bots that depend on the matrix-protection-suite and interface-manager. Since this is essentially glue code that hasn't made its way into abstractions yet that other bots would need to duplicate to get started.
And we're doing this because we're thinking of making a contributor bot for fun primarily, gathering feedback, and encouraging testing .
- Split out the room discovery notifications into their own matrix room.
- Ensure that information for room creator and the server (that the room create is signed with) are stored in the room info. And add ways to look those up in the future.
- Stop content violation notifications appearing in takedown/shutdown
- disable room discovery by default while we work out how to pipe it into a new room
- show status of takedown protections in the takedown command
- clarify a comment about the implementation of blocking invintations
We really need to figure out how to let protections put all their output into a room.
It is too noisy and i don't think people have time to review it. In a
moment i will try see if i can create a new room for the protection at
startup in a moment.
* Improve room shutdown flows.
- The shutdown command now has a `--notify` option for whether to send
the violation notification.
- We use shutdown V1 because V2 doesn't propagate leave events to clients
properly. Which sucks.
* Fix flakey shutdown test.
So this was never working it was just catching the original message
containing the command by speed of shutdown V2.
Fixes a tonne of shite mare.
Importantly https://github.com/the-draupnir-project/Draupnir/issues/845.
And something @ll-SKY-ll mentioned in the draupnir room regarding the new MentionLimitProtection.
Added
- Quote syntax to quote strings.
- Boolean presentation type and translator to string.
Fixed
- Added a pathway to create negative integers.
- Send a warning message when the event gets removed.
- Ban on the second infraction.
- Make it an option as to whether the message gets split.
- The config file won't work anymore can't fix that because wuh we can't have both as the source of truth........ unless we differentiate based on the timestamp but that requires infrastructure changes.
Homeserver Admin: Restrict resident users automatically based on watched policy rooms
We introduce a new concept "restriction" which basically means "can a user send events from this account". Which is important when purging the messages sent from a user while deactivating their account.
We introduce a new protection, the `HomeserverUserPolicyApplication` protection which suspends users automatically when resident users match a policy from watched policy rooms. If the policy contains a reason for `config.automaticallyRedactForReasons`, then we prompt to do a purging deactivate (redact -> deactivate).
Users are also unsuspended as policies are removed.
We also introduce a `--purge-messages` and `--no-confirm` option to the `deactivate` command. This means that the command can now use the user redaction endpoint to redact messages and will shadowban the user while it does this if their account isn't already restricted. The addition of `--no-confirm` means that we now show a preview every time you run the deactivate command where you can review the user details before confirming the deactivation.
Follow up 1: https://github.com/the-draupnir-project/Draupnir/issues/813
Follow up 2: https://github.com/the-draupnir-project/Draupnir/issues/814
Gnuxie