From d3efb2ff5c9df02ff6f27a895e89867cbdad080c Mon Sep 17 00:00:00 2001 From: William Kray Date: Thu, 10 Apr 2025 23:12:07 -0700 Subject: [PATCH] update readme with info about verify-migrate command and warning --- README.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index b534ade..1e28ef1 100644 --- a/README.md +++ b/README.md @@ -148,7 +148,7 @@ please keep in mind that wordlist-based censorship is problematic and may redact algorithm that is perfect is impossible. consider configuring your community such that censorship need only be applied in a limited subset of rooms. -# user verification +## user verification configure your rooms (all, or a list of room-ids) to use the `check_if_human` setting. use this in conjunction with a room power-level configuration that requires elevated permission to send messages. for example, a "waiting-room" @@ -170,6 +170,13 @@ significant spam in your rooms. every permitted user goes in the state event, so will become problematic and expensive for very large rooms... strong recommend not to use this if you expect to have thousands of room members. +if you enable user verification in an existing room, but you don't want to disrupt the +current users' ability to send messages, you can use the `!community verify-migrate` +command to set permissions correctly. **DO NOT DO THIS IN LARGE ROOMS**. if you have more +than a handful of people, consider how many of them actually say anything in a given day +and whether or not it's worth filling your state event with them. consider alternative +options. + # installation install this like any other maubot plugin: zip the contents of this repo into a file and upload via the web interface,