Mercurial > prosody-modules
view mod_admin_blocklist/README.markdown @ 5173:460f78654864
mod_muc_rtbl: also filter messages
This was a bit tricky because we don't want to run the JIDs
through SHA256 on each message. Took a while to come up with this
simple plan of just caching the SHA256 of the JIDs on the
occupants.
This will leave some dirt in the occupants after unloading the
module, but that should be ok; once they cycle the room, the
hashes will be gone.
This is direly needed, otherwise, there is a tight race between
the moderation activities and the actors joining the room.
author | Jonas Schäfer <jonas@wielicki.name> |
---|---|
date | Tue, 21 Feb 2023 21:37:27 +0100 |
parents | 96e83b4a93f7 |
children |
line wrap: on
line source
--- summary: Block s2s connections based on admin blocklists ... This module uses the blocklists set by admins for blocking s2s connections. So if an admin blocks a bare domain using [Blocking Command][xep191] via [mod\_blocklist][doc:modules:mod_blocklist] then no s2s connections will be allowed to or from that domain. # Configuring ## Prosody 0.12 Starting with Prosody 0.12, the role or roles that determine whether a particular users blocklist is used can be configured: ```lua -- This is the default: admin_blocklist_roles = { "prosody:operator", "prosody:admin" } ``` ## Prosody 0.11 In Prosody 0.11 the [`admins`][doc:admins] setting is used.