Software /
code /
prosody-modules
File
mod_muc_batched_probe/README.markdown @ 5810: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 |
parent | 4000:d56b3c0195a8 |
line wrap: on
line source
# mod_muc_batched_probe This module allows you to probe the presences of multiple MUC occupants or members. XEP-0045 makes provision for MUC presence probes, which allows an entity to probe for the presence information of a MUC occupant (or offline member). See here: https://xmpp.org/extensions/xep-0045.html#bizrules-presence This module creates the possibility to probe with a single IQ stanza the presence information of multiple JIDs, instead of having to send out a presence probe stanza per JID. The IQ stanza needs to look as follows: ``` <iq from="hag66@shakespeare.lit/pda" id="zb8q41f4" to="chat.shakespeare.lit" type="get"> <query xmlns="http://jabber.org/protocol/muc#user"> <item jid="hecate@shakespeare.lit"/> <item jid="crone1@shakespeare.lit"/> <item jid="wiccarocks@shakespeare.lit"/> <item jid="hag66@shakespeare.lit"/> </query> </iq> ``` ## Configuration Under your MUC component, add `muc_batched_probe` to `modules_enabled` ``` Component "conference.example.org" "muc" modules_enabled = { "muc_batched_probe"; } ``` ## Client Support Converse.js has a plugin which supports this feature. https://www.npmjs.com/package/@converse-plugins/muc-presence-probe