Software /
code /
prosody-modules
File
mod_muc_archive/README.markdown @ 4941:e7b9bc629ecc
mod_rest: Add special handling to catch MAM results from remote hosts
Makes MAM queries to remote hosts works.
As the comment says, MAM results from users' local archives or local
MUCs are returned via origin.send() which is provided in the event and
thus already worked. Results from remote hosts go via normal stanza
routing and events, which need this extra handling to catch.
This pattern of iq-set, message+, iq-result is generally limited to MAM.
Closest similar thing might be MUC join, but to really handle that you
would need the webhook callback mechanism.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Mon, 16 May 2022 19:47:09 +0200 |
parent | 3957:7e96b95924bd |
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 ------ -----