Software /
code /
prosody-modules
File
mod_muc_moderation/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 |
parent | 5127:be859bfdd44e |
child | 5484:bb083e9f78dd |
line wrap: on
line source
# Introduction This module implements [XEP-0425: Message Moderation]. # Usage Moderation is done via a supporting client and requires a `moderator` role in the channel / group chat. # Configuration Example [MUC component][doc:chatrooms] configuration: ``` {.lua} VirtualHost "channels.example.com" "muc" modules_enabled = { "muc_mam", "muc_moderation", } ``` # Compatibility - Basic functionality with Prosody 0.11.x and later - Full functionality with Prosody 0.12.x and `internal` or `sql` storage^[Replacing moderated messages with tombstones requires new storage API methods.] ## Clients - [Converse.js](https://conversejs.org/) - [Gajim](https://dev.gajim.org/gajim/gajim/-/issues/10107) - [clix](https://code.zash.se/clix/rev/6c1953fbe0fa) ### Feature requests - [Conv](https://github.com/iNPUTmice/Conversations/issues/3722)[ersa](https://github.com/iNPUTmice/Conversations/issues/3920)[tions](https://github.com/iNPUTmice/Conversations/issues/4227) - [Dino](https://github.com/dino/dino/issues/1133) - [Poezio](https://lab.louiz.org/poezio/poezio/-/issues/3543) - [Profanity](https://github.com/profanity-im/profanity/issues/1336)