Mercurial > prosody-modules
diff mod_cloud_notify/README.markdown @ 3055:6abee021d9db
mod_cloud_notify: Limit number of devices to 5 and change some default settings
author | tmolitor <thilo@eightysoft.de> |
---|---|
date | Mon, 28 May 2018 05:28:07 +0200 |
parents | df86ce6bb0b4 |
children | 2a918a8c47db |
line wrap: on
line diff
--- a/mod_cloud_notify/README.markdown Mon May 28 05:27:03 2018 +0200 +++ b/mod_cloud_notify/README.markdown Mon May 28 05:28:07 2018 +0200 @@ -46,12 +46,13 @@ Configuration ============= - Option Default Description - ------------------------------------ --------- --------------------------------------------------------------------------------------------------------------- - `push_notification_with_body` `false` Whether or not to send the message body to remote pubsub node. - `push_notification_with_sender` `false` Whether or not to send the message sender to remote pubsub node. - `push_max_errors` `50` How much persistent push errors are tolerated before notifications for the identifier in question are disabled - `push_notification_important_body` `` The body text to use when the stanza is important (see above), no message body is sent if this is empty + Option Default Description + ------------------------------------ ----------------- ------------------------------------------------------------------------------------------------------------------- + `push_notification_with_body` `false` Whether or not to send the message body to remote pubsub node. + `push_notification_with_sender` `false` Whether or not to send the message sender to remote pubsub node. + `push_max_errors` `16` How much persistent push errors are tolerated before notifications for the identifier in question are disabled + `push_notification_important_body` `New Message!` The body text to use when the stanza is important (see above), no message body is sent if this is empty + `push_max_devices` `5` The number of allowed devices per user (the oldest devices are automatically removed if this threshold is reached) There are privacy implications for enabling these options because plaintext content and metadata will be shared with centralized servers