Mercurial > prosody-modules
view mod_muc_rtbl/README.md @ 5533:09311a8a3cfa
mod_firewall: spam-blocking.pfw: Remove requirement for invites to have no body
Some clients (e.g. Gajim) send a body, which I guess makes sense.
The bare JID sender check should already make it hard to bypass this (i.e.
a normal client putting muc#user into a normal chat message shouldn't bypass
the usual message filters).
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Thu, 08 Jun 2023 12:20:34 +0100 |
parents | 62a65c52c3f5 |
children |
line wrap: on
line source
--- summary: rockspec: dependencies: - mod_pubsub_subscription labels: - Stage-Alpha ... This module subscribes to a real-time blocklist using pubsub (XEP-0060). As entries are added and removed from the blocklist, it immediately updates a local service-wide ban list. # Configuring Load this module on your existing MUC component like so: ```lua Component "channels.example.com" "muc" modules_enabled = { -- other modules etc "muc_rtbl"; } ``` Then there are two options, which must be set under the component or in the global section of your config: ``` muc_rtbl_jid = "rtbl.example" muc_rtbl_node = "muc_bans_sha256" ``` # Compatibility Should work with Prosody >= 0.11.x # Developers ## Protocol This version of mod_muc_rtbl assumes that the pubsub node contains one item per blocked JID. The item id should be the SHA256 hash of the JID to block. The payload is not currently used, but it is recommend to use a XEP-0377 report element as the payload.