Mercurial > prosody-modules
view mod_muc_defaults/README.markdown @ 5787:e79f9dec35c0
mod_c2s_conn_throttle: Reduce log level from error->info
Our general policy is that "error" should never be triggerable by remote
entities, and that it is always about something that requires admin
intervention. This satisfies neither condition.
The "warn" level can be used for unexpected events/behaviour triggered by
remote entities, and this could qualify. However I don't think failed auth
attempts are unexpected enough.
I selected "info" because it is what is also used for other notable session
lifecycle events.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Thu, 07 Dec 2023 15:46:50 +0000 |
parents | a1f8cc591b66 |
children |
line wrap: on
line source
# mod_muc_defaults Creates MUCs with default configuration settings upon Prosody startup. ## Configuration Under your MUC component, add a `default_mucs` option with the relevant settings. ``` Component "conference.example.org" "muc" modules_enabled = { "muc_defaults"; } default_mucs = { { jid_node = "trollbox", affiliations = { admin = { "admin@example.org", "superuser@example.org" }, owner = { "owner@example.org" }, visitors = { "visitor@example.org" } }, config = { name = "General Chat", description = "Public chatroom with no particular topic", allow_member_invites = false, change_subject = false, history_length = 40, lang = "en", logging = true, members_only = false, moderated = false, persistent = true, public = true, public_jids = true } } }; ```