Mercurial > prosody-modules
view mod_muc_adhoc_bots/README.markdown @ 5951:d6a695abb33c
mod_ping_muc: Delay ping a configurable amount of time
If a server is restarting, checking immediately before it has a chance
to complete its restart and get ready would often fail, preventing the
possibility of transparent restarts as supported by Prosody's mod_muc.
Reconnecting immediately when a connection is closed for being idle, or
because the remote server is trying to reclaim some resources, is also
counter-productive as the connection may fail.
Also, if there is some Internet routing problem affecting s2s, it may
help to wait a bit before checking, in case the problem resolved itself
in the mean time.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Sun, 11 Aug 2024 16:10:24 +0200 |
parents | 7a4a6ded2bd6 |
children |
line wrap: on
line source
--- labels: - Stage-Alpha summary: Install adhoc command bots in MUCs --- # Introduction This module allows you to "install" bots on a MUC service (via config for now, via adhoc command and on just one MUC to follow). All the adhoc commands defined on the bot become adhoc commands on the service's MUCs, and the bots can send XEP-0356 messages to the MUC to send messages as any participant. # Configuration List all bots to install. You must specify full JID. adhoc_bots = { "some@bot.example.com/bot" } And enable the module on the MUC service as usual modules_enabled = { "muc_adhoc_bots" }