Software /
code /
prosody-modules
File
mod_muc_log/README.markdown @ 5405:c7a5caad28ef
mod_http_oauth2: Enforce response type encoded in client_id
The client promises to only use this response type, so we should hold
them to that.
This makes it fail earlier if the response type is disabled or the
client is trying to use one that it promised not to use. Better than
failing after login and consent.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 02 May 2023 16:31:25 +0200 |
parent | 3458:adf84d6a457d |
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+.