Mercurial > prosody-modules
view mod_muc_limits/README.md @ 6258:06fbbd45ba75
mod_cloud_notify: Readme: fix links and labels that were removed in the last commit
diff --git a/mod_cloud_notify/README.md b/mod_cloud_notify/README.md
--- a/mod_cloud_notify/README.md
+++ b/mod_cloud_notify/README.md
@@ -1,3 +1,9 @@
+----
+-labels:
+-- 'Stage-Beta'
+-summary: 'XEP-0357: Cloud push notifications'
+----
+
# Introduction
This module enables support for sending "push notifications" to clients
@@ -32,15 +38,15 @@ notification to your device. When your d
it will display it or wake up the app so it can connect to XMPP and
receive any pending messages.
-This protocol is described for developers in \[XEP-0357: Push
-Notifications\].
+This protocol is described for developers in [XEP-0357: Push
+Notifications].
-For this module to work reliably, you must have \[mod_smacks\],
-\[mod_mam\] and \[mod_carbons\] also enabled on your server.
+For this module to work reliably, you must have [mod_smacks],
+[mod_mam] and [mod_carbons] also enabled on your server.
Some clients, notably Siskin and Snikket iOS need some additional
extensions that are not currently defined in a standard XEP. To support
-these clients, see \[mod_cloud_notify_extensions\].
+these clients, see [mod_cloud_notify_extensions].
# Configuration
@@ -58,18 +64,18 @@ these clients, see \[mod_cloud_notify_ex
# Internal design notes
App servers are notified about offline messages, messages stored by
-\[mod_mam\] or messages waiting in the smacks queue. The business rules
+[mod_mam] or messages waiting in the smacks queue. The business rules
outlined
[here](//mail.jabber.org/pipermail/standards/2016-February/030925.html)
are all honored[^2].
-To cooperate with \[mod_smacks\] this module consumes some events:
+To cooperate with [mod_smacks] this module consumes some events:
`smacks-ack-delayed`, `smacks-hibernation-start` and
`smacks-hibernation-end`. These events allow this module to send out
notifications for messages received while the session is hibernated by
-\[mod_smacks\] or even when smacks acknowledgements for messages are
+[mod_smacks] or even when smacks acknowledgements for messages are
delayed by a certain amount of seconds configurable with the
-\[mod_smacks\] setting `smacks_max_ack_delay`.
+[mod_smacks] setting `smacks_max_ack_delay`.
The `smacks_max_ack_delay` setting allows to send out notifications to
clients which aren't already in smacks hibernation state (because the
| author | Menel <menel@snikket.de> |
|---|---|
| date | Fri, 13 Jun 2025 10:44:37 +0200 |
| parents | 0206d32c56b7 |
| children |
line wrap: on
line source
--- labels: - 'Stage-Beta' summary: 'Impose rate-limits on a MUC' ... Introduction ============ This module allows you to control the maximum rate of 'events' in a MUC room. This makes it useful to prevent room floods (whether malicious or accidental). Details ======= This module limits the following events: - Room joins - Nick changes - Status changes - Messages (including private messages) The limit is for the room as a whole, not individual occupants in the room. Users with an affiliation (members, admins and owners) are not limited. Configuration ============= Add the module to the MUC host (not the global modules\_enabled): ```lua Component "conference.example.com" "muc" modules_enabled = { "muc_limits" } ``` You can define (globally or per-MUC component) the following options: Name Default value Description --------------------------- --------------- ---------------------------------------------------------- muc_event_rate 0.5 The maximum number of events per second. muc_burst_factor 6 Allow temporary bursts of this multiple. muc_max_nick_length 23 The maximum allowed length of user nicknames muc_max_char_count 5664 The maximum allowed number of bytes in a message muc_max_line_count 23 The maximum allowed number of lines in a message muc_limit_base_cost 1 Base cost of sending a stanza muc_line_count_multiplier 0.1 Additional cost of each newline in the body of a message For more understanding of how these values are used, see the algorithm section below. Algorithm ========= A certain number of events are allowed per second, given by muc\_event\_rate. An event rate of 1 allows one event per second, and event rate of 3 allows three events per second, and 0.5 allows one event every two seconds, and so on. Obviously MUC conversations are not exactly steady streams of events. Sometimes multiple people will talk at once. This is handled by the muc\_burst\_factor option. A burst factor of 2 will allow 2 times as many events at once, for 2 seconds, before throttling will be triggered. A factor of 5, 5 times as many events for 5 seconds. When the limit is reached, an error response will be generated telling the user the MUC is overactive, and asking them to try again. Compatibility ============= ------- ------- trunk* Works 0.12 Works ------- ------- *as of 2024-10-22
