Mercurial > prosody-modules
annotate mod_register_redirect/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 | fe081789f7b5 |
| children |
| rev | line source |
|---|---|
| 1803 | 1 --- |
| 2 labels: | |
| 3 - 'Stage-Stable' | |
| 4 summary: 'XEP-077 IBR Registration Redirect.' | |
| 5 ... | |
| 6 | |
| 7 Introduction | |
| 8 ------------ | |
| 9 | |
| 10 Registration Redirect as explained in the [IBR | |
| 11 XEP](http://xmpp.org/extensions/xep-0077.html#redirect). | |
| 12 | |
| 13 Details | |
| 14 ------- | |
| 15 | |
| 16 This module shows instructions on how to register to the server, should | |
| 17 it be necessary to perform it through other means Out-Of-Band or not, | |
| 18 and also let's registrations origining from ip addresses in the | |
| 19 whitelist to go through normally. | |
| 20 | |
| 21 Usage | |
| 22 ----- | |
| 23 | |
| 24 Copy the module file into your Prosody modules directory. | |
| 25 | |
| 26 The module will work "out of the box" as long as at least an admin entry | |
| 27 is specified (see admins = {} option into prosody's documentation).These | |
| 28 are the optional parameters you can specify into your global | |
| 29 server/hostname configuration: | |
| 30 | |
| 31 registration_whitelist = { "*your whitelisted web server ip address*" } | |
|
5727
372b6c4bf409
mod_register_redirect: docs: Fix typo in example (thanks melvo)
Matthew Wild <mwild1@gmail.com>
parents:
2785
diff
changeset
|
32 registration_url = "*your web registration page url*" |
| 1803 | 33 registration_text = "Your custom instructions banner here" |
| 34 registration_oob = true (default) or false, in the case there's no applicable OOB method (e.g. the server admins needs to be contacted by phone) | |
| 35 | |
| 36 To not employ any whitelisting (i.e. registration is handled | |
| 37 externally). | |
| 38 | |
| 39 no_registration_whitelist = true | |
| 40 | |
| 41 Compatibility | |
| 42 ------------- | |
| 43 | |
| 2785 | 44 ------ -------------- |
| 45 0.10 Works | |
| 46 0.9 Works | |
| 47 0.8 Works | |
| 48 0.7 Might not work | |
| 49 0.6 Doesn't work | |
| 50 0.5 Doesn't work | |
| 51 ------ -------------- | |
| 1803 | 52 |
