Mercurial > prosody-modules
view mod_ping_muc/README.md @ 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 | 0772facc786f |
children | c094eabdb30f |
line wrap: on
line source
--- summary: Yet another MUC reliability module rockspec: dependencies: - mod_track_muc_joins labels: - Stage-Alpha ... This module reacts to [server-to-server][doc:s2s] connections closing by performing [XEP-0410: MUC Self-Ping] from the server side to check if users are still connected to MUCs they have joined according [mod_track_muc_joins]. If it can't be confirmed that the user is still joined then their client devices are notified about this allowing them to re-join. # Installing ``` prosodyctl install mod_ping_muc ``` # Configuring No configuration. Enable as a regular module in [`modules_enabled`][doc:modules_enabled] globally or under a `VirtualHost`: ```lua modules_enabled = { -- other modules etc "track_muc_joins", "ping_muc", } ``` # Compatibility Requires Prosody 0.12.x or trunk