Mercurial > prosody-modules
view mod_storage_muc_log/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 | 058844edcaaf |
children |
line wrap: on
line source
--- labels: - 'Stage-Alpha' - ArchiveStorage summary: 'Storage module using mod\_muc\_log data with new stanza archive API' --- Introduction ============ [mod\_muc\_log] provided logging of chatrooms running on the server to Prosody's data store. This module gives access to this data using the 0.10+ stanza archive API, allowing legacy log data to be used with [mod\_mam\_muc] and [mod\_http\_muc\_log]. Details ======= Replace [mod\_muc\_log] and [mod\_muc\_log\_http] in your config with ``` {.lua} Component "conference.example.org" "muc" modules_enabled = { -- "muc_log"; -- functionality replaced by mod_mam_muc + mod_storage_muc_log "mam_muc"; -- Does logging to storage backend configured below -- "muc_log_http"; -- Replaced by the mod_http_muc_log "http_muc_log"; } storage = { muc_log = "muc_log"; } ``` Compatibility ============= version status --------- --------------- 0.9 unknown 0.10 works 0.11 does not work