prosody-modules
96e83b4a93f7
mod_admin_blocklist/README.markdown

Find changesets by keywords by author, files, the commit message, revision number or hash, or revset expression.

Software / code / prosody-modules

Comparison

mod_admin_blocklist/README.markdown @ 5017:96e83b4a93f7

mod_admin_blocklist: Add config option for which role(s) to consider (0.12+) Fixes that in trunk, a "prosody:operator" (formerly a global admin) is not considered a "prosody:admin", so those were not included in the set.
author Kim Alvefur <zash@zash.se>
date Sat, 27 Aug 2022 16:36:22 +0200
parent 2316:2a2de19413e7
comparison
equal deleted inserted replaced
5016:964de9997552 5017:96e83b4a93f7
6 connections. 6 connections.
7 7
8 So if an admin blocks a bare domain using [Blocking Command][xep191] 8 So if an admin blocks a bare domain using [Blocking Command][xep191]
9 via [mod\_blocklist][doc:modules:mod_blocklist] then no s2s connections 9 via [mod\_blocklist][doc:modules:mod_blocklist] then no s2s connections
10 will be allowed to or from that domain. 10 will be allowed to or from that domain.
11
12 # Configuring
13
14 ## Prosody 0.12
15
16 Starting with Prosody 0.12, the role or roles that determine whether a
17 particular users blocklist is used can be configured:
18
19 ```lua
20 -- This is the default:
21 admin_blocklist_roles = { "prosody:operator", "prosody:admin" }
22 ```
23
24 ## Prosody 0.11
25
26 In Prosody 0.11 the [`admins`][doc:admins] setting is used.