Software /
code /
prosody-modules
File
mod_muc_log_http/README.markdown @ 5185:09d6bbd6c8a4
mod_http_oauth2: Fix treatment of 'redirect_uri' parameter in code flow
It's optional and the one stored in the client registration should
really be used instead. RFC 6749 says an URI provided as parameter MUST
be validated against the stored one but does not say how.
Given that the client needs their secret to proceed, it seems fine to
leave this for later.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Thu, 02 Mar 2023 22:00:42 +0100 |
parent | 1821:79b9bd84b91c |
line wrap: on
line source
--- labels: - 'Stage-Beta' summary: Provides a web interface to stored chatroom logs ... Introduction ============ This module provides a built-in web interface to view chatroom logs stored by [mod\_muc\_log](mod_muc_log.html). Installation ============ Just copy the folder muc\_log\_http as it is, into the modules folder of your Prosody installation. Configuration Details ===================== Example configuration: Component "conference.example.com" "muc" modules_enabled = { ..... "muc_log"; "muc_log_http"; ..... } muc_log_http = { -- These are the defaults show_join = true; show_presences = true; show_status = true; theme = "prosody"; url_base = "muc_log"; } **show\_join** sets the default for showing joins or leaves. **show\_status** sets the default for showing status changes. The web interface would then be reachable at the address: http://conference.example.com:5280/muc_log/ TODO ==== - Log bans correctly - Quota \~ per day ?! - Testing testing :)