Mercurial > prosody-modules
view mod_muc_archive/README.markdown @ 5536:96dec7681af8
mod_firewall: Update user marks to store instantly via map store
The original approach was to keep marks in memory only, and persist them at
shutdown. That saves I/O, at the cost of potentially losing marks on an
unclean shutdown.
This change persists marks instantly, which may have some performance overhead
but should be more "correct".
It also splits the marking/unmarking into an event which may be watched or
even fired by other modules.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Thu, 08 Jun 2023 16:20:42 +0100 |
parents | 7e96b95924bd |
children |
line wrap: on
line source
--- labels: - 'Stage-Beta' summary: Log MUC messages to disk ... # Introduction This module logs the conversations of chatrooms running on the server to Prosody's data store. This is a fork of [mod_muc_log](https://modules.prosody.im/mod_muc_log.html) which uses the newer storage API. This allows you to also log messages to a SQL backend. ## Changes between mod_muc_archive and mod_muc_log: - Use newer module storage API so that you can also store in SQL - Adhere to config option `muc_log_all_rooms` (also used by mod_muc_mam) - Add affiliation information in the logged stanza - Remove code that set (and then removed) an "alreadyJoined" dummy element NOTE: The changes are unlikely to be entirely backwards compatible because the stanza being logged is no longer wrapped with `<stanza time=...>`. Details ======= mod\_muc\_archive must be loaded individually for the components that need it. Assuming you have a MUC component already running on conference.example.org then you can add muc\_archive to it like so: Component "conference.example.org" "muc" modules_enabled = { "muc_archive"; } Compatibility ============= ------ ----- 0.11 Works ------ -----