Software /
code /
prosody-modules
File
mod_muc_log/README.md @ 6159:82a10e21b7f9
mod_anti_spam: prosody 0.12 compat
diff --git a/mod_anti_spam/trie.lib.lua b/mod_anti_spam/trie.lib.lua
--- a/mod_anti_spam/trie.lib.lua
+++ b/mod_anti_spam/trie.lib.lua
@@ -1,4 +1,4 @@
-local bit = require "prosody.util.bitcompat";
+local bit = require "util.bitcompat";
local trie_methods = {};
local trie_mt = { __index = trie_methods };
author | Menel <menel@snikket.de> |
---|---|
date | Sun, 19 Jan 2025 09:48:10 +0100 |
parent | 6003:fe081789f7b5 |
child | 6197:ba8f5cdc1676 |
line wrap: on
line source
--- labels: - 'Stage-Beta' summary: Log chatroom messages to disk ... Introduction ============ This module logs the conversation of chatrooms running on the server to Prosody's data store. To view them you will need a module such as [mod\_muc\_log\_http](mod_muc_log_http.html). Details ======= mod\_muc\_log 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\_log to it like so: Component "conference.example.org" "muc" modules_enabled = { "muc_log"; } Logging is not enabled by default. In 0.9+ logging can be enabled per room in the room config form. To enable logging in older versions, or to enable logging by default for all rooms, set muc_log_by_default = true -- Log all rooms by default Compatibility ============= ------ --------------- 0.6 Works 0.7 Works 0.8 Works 0.9 Works 0.10 Works 0.11 Does not work ------ --------------- **Note** that per-room configuration only works in 0.9+.