Mercurial > prosody-modules
view mod_muc_archive/README.markdown @ 4579:b305814bd930
mod_muc_dicebot: A thing to roll dice
Do you see what happens, Jitsi? Do you see what happens when you
make it hard for me to use a proper bot? This is what happens,
Jitsi. This is what happens when you meet a stranger in the alps!
Ahem. In all seriousness, this is more of a quick hack than
anything else. It will look for `.r` in MUC messages and if it
finds it, it'll interpret it as an instruction to roll a few
dice. Injects the results in the body of the message. Eats the
message alive if it is malformed.
author | Jonas Schäfer <jonas@wielicki.name> |
---|---|
date | Sat, 29 May 2021 15:17:05 +0200 |
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 ------ -----