File

mod_groups_internal/README.md @ 6301:fa45ae704b79

mod_cloud_notify: Update Readme 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,109 +1,106 @@ ---- -labels: -- 'Stage-Beta' -summary: 'XEP-0357: Cloud push notifications' ---- +# Introduction -Introduction -============ +This module enables support for sending "push notifications" to clients +that need it, typically those running on certain mobile devices. -This module enables support for sending "push notifications" to clients that -need it, typically those running on certain mobile devices. +As well as this module, your client must support push notifications (the +apps that need it generally do, of course) and the app developer's push +gateway must be reachable from your Prosody server (this happens over a +normal XMPP server-to-server 's2s' connection). -As well as this module, your client must support push notifications (the apps -that need it generally do, of course) and the app developer's push gateway -must be reachable from your Prosody server (this happens over a normal XMPP -server-to-server 's2s' connection). - -Details -======= +# Details Some platforms, notably Apple's iOS and many versions of Android, impose -limits that prevent applications from running or accessing the network in the -background. This makes it difficult or impossible for an XMPP application to -remain reliably connected to a server to receive messages. - -In order for messaging and other apps to receive notifications, the OS vendors -run proprietary servers that their OS maintains a permanent connection to in -the background. Then they provide APIs to application developers that allow -sending notifications to specific devices via those servers. +limits that prevent applications from running or accessing the network +in the background. This makes it difficult or impossible for an XMPP +application to remain reliably connected to a server to receive +messages. -When you connect to your server with an app that requires push notifications, -it will use this module to set up a "push registration". When you receive -a message but your device is not connected to the server, this module will -generate a notification and send it to the push gateway operated by your -application's developers). Their gateway will then connect to your device's -OS vendor and ask them to forward the notification to your device. When your -device receives the notification, it will display it or wake up the app so it -can connect to XMPP and receive any pending messages. +In order for messaging and other apps to receive notifications, the OS +vendors run proprietary servers that their OS maintains a permanent +connection to in the background. Then they provide APIs to application +developers that allow sending notifications to specific devices via +those servers. -This protocol is described for developers in [XEP-0357: Push Notifications]. +When you connect to your server with an app that requires push +notifications, it will use this module to set up a "push registration". +When you receive a message but your device is not connected to the +server, this module will generate a notification and send it to the push +gateway operated by your application's developers). Their gateway will +then connect to your device's OS vendor and ask them to forward the +notification to your device. When your device receives the notification, +it will display it or wake up the app so it can connect to XMPP and +receive any pending messages. -For this module to work reliably, you must have [mod_smacks], [mod_mam] and -[mod_carbons] also enabled on your server. +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. -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]. +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\]. -Configuration -============= +# Configuration - Option Default Description - ------------------------------------ ----------------- ------------------------------------------------------------------------------------------------------------------- - `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_errors` `16` How much persistent push errors are tolerated before notifications for the identifier in question are disabled - `push_max_devices` `5` The number of allowed devices per user (the oldest devices are automatically removed if this threshold is reached) - `push_max_hibernation_timeout` `259200` (72h) Number of seconds to extend the smacks timeout if no push was triggered yet (default: 72 hours) - `push_notification_with_body` (\*) `false` Whether or not to send the real message body to remote pubsub node. Without end-to-end encryption, enabling this may expose your message contents to your client developers and OS vendor. Not recommended. - `push_notification_with_sender` (\*) `false` Whether or not to send the real message sender to remote pubsub node. Enabling this may expose your contacts to your client developers and OS vendor. Not recommended. + Option Default Description + -------------------------------------- ---------------- ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- + `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_errors` `16` How much persistent push errors are tolerated before notifications for the identifier in question are disabled + `push_max_devices` `5` The number of allowed devices per user (the oldest devices are automatically removed if this threshold is reached) + `push_max_hibernation_timeout` `259200` (72h) Number of seconds to extend the smacks timeout if no push was triggered yet (default: 72 hours) + `push_notification_with_body` (\*) `false` Whether or not to send the real message body to remote pubsub node. Without end-to-end encryption, enabling this may expose your message contents to your client developers and OS vendor. Not recommended. + `push_notification_with_sender` (\*) `false` Whether or not to send the real message sender to remote pubsub node. Enabling this may expose your contacts to your client developers and OS vendor. Not recommended. -(\*) There are privacy implications for enabling these options. +(\*) There are privacy implications for enabling these options.[^1] -Internal design notes -===================== +# 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 outlined [here](//mail.jabber.org/pipermail/standards/2016-February/030925.html) are all honored[^2]. +App servers are notified about offline messages, messages stored by +\[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: -`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 delayed by a certain amount of seconds -configurable with the [mod_smacks] setting `smacks_max_ack_delay`. +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 +delayed by a certain amount of seconds configurable with the +\[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 read timeout or -connection close didn't already happen) but also aren't responding to acknowledgement -request in a timely manner. This setting thus allows conversations to be smoother -under such circumstances. +The `smacks_max_ack_delay` setting allows to send out notifications to +clients which aren't already in smacks hibernation state (because the +read timeout or connection close didn't already happen) but also aren't +responding to acknowledgement request in a timely manner. This setting +thus allows conversations to be smoother under such circumstances. -The new event `cloud-notify-ping` can be used by any module to send out a cloud -notification to either all registered endpoints for the given user or only the endpoints -given in the event data. +The new event `cloud-notify-ping` can be used by any module to send out +a cloud notification to either all registered endpoints for the given +user or only the endpoints given in the event data. -The config setting `push_notification_important_body` can be used to specify an alternative -body text to send to the remote pubsub node if the stanza is encrypted or has a body. -This way the real contents of the message aren't revealed to the push appserver but it -can still see that the push is important. -This is used by Chatsecure on iOS to send out high priority pushes in those cases for example. +The config setting `push_notification_important_body` can be used to +specify an alternative body text to send to the remote pubsub node if +the stanza is encrypted or has a body. This way the real contents of the +message aren't revealed to the push appserver but it can still see that +the push is important. This is used by Chatsecure on iOS to send out +high priority pushes in those cases for example. -Compatibility -============= - -**Note:** This module should be used with Lua 5.2 and higher. Using it with -Lua 5.1 may cause push notifications to not be sent to some clients. +# Compatibility ------- ----------------------------------------------------------------------------- - trunk Works - 0.12 Works - 0.11 Works - 0.10 Works - 0.9 Support dropped, use last supported version [675726ab06d3](//hg.prosody.im/prosody-modules/raw-file/675726ab06d3/mod_cloud_notify/mod_cloud_notify.lua) ------- ----------------------------------------------------------------------------- +**Note:** This module should be used with Lua 5.2 and higher. Using it +with Lua 5.1 may cause push notifications to not be sent to some +clients. + ------- ----------------------------------------------------------------- + trunk Works as of 25-06-13 + 13 Works + 0.12 Works + ------- ----------------------------------------------------------------- -[^1]: The service which is expected to forward notifications to something like Google Cloud Messaging or Apple Notification Service -[^2]: [business_rules.markdown](//hg.prosody.im/prosody-modules/file/tip/mod_cloud_notify/business_rules.markdown) +[^1]: The service which is expected to forward notifications to + something like Google Cloud Messaging or Apple Notification Service + +[^2]: [business_rules.md](//hg.prosody.im/prosody-modules/file/tip/mod_cloud_notify/business_rules.md)
author Menel <menel@snikket.de>
date Fri, 13 Jun 2025 10:36:52 +0200
parent 6183:d0a117e11cb8
child 6211:750d64c47ec6
line wrap: on
line source

---
labels:
- 'Stage-Beta'
summary: Equivalent of mod_groups but without a configuration file
---

## Introduction

This module is functionally similar to [`mod_groups`], but it differs by working without a configuration file (allowing changes without a restart of the server) and by permanently adding users to each other's contact lists. To paraphrase [`mod_groups`]:

> `mod_groups_internal` was designed to allow administrators to create virtual groups of users that automatically see each other in their contact lists. There is no need for the user to authorise these contacts in their contact list - this is done automatically on the server.
>
> As an example, if you have a team of people working together on a project, you can create a group for that team. They will automatically be added to each others' contact lists, and the list can easily be modified on the server at any time to add and remove people.

::: {.alert .alert-info}
On `user-deleted` events, `mod_groups_internal` will automatically remove the deleted user from every group they were part of.
:::

## Setup

```lua
modules_enabled = {
    -- Other modules
    "groups_internal"; -- Enable mod_groups_internal
}
```

## Configuration

| Option | Type | Default | Notes |
| ------ | ---- | ------- | ----- |
| `groups_muc_host` | string? | nil | Host where the group chats will be created. |

## Usage

### Exposed functions

- #### `create(group_info, create_default_muc, group_id)` {#create}

  Creates a new group, optionally creating a default MUC chat on [`groups_muc_host`](#configuration).

  **Parameters:**

  1. `group_info: { name: string }`
  2. `create_default_muc: boolean | nil`: Whether or not to create the default MUC chat. Defaults to `false`.
  3. `group_id: string | nil`: The desired group JID node part. Defaults to [`util.id.short`](https://prosody.im/doc/developers/util/id) (9-chars URL-safe base64).

  **Returns:** `group_id: string | nil, error: string`

- #### `get_info(group_id)` {#get_info}

  Retrieves information about a group.

  **Parameters:**

  1. `group_id: string`: Node part of the group's JID.

  **Returns:**

  ```lua
  group_info: {
    name: string,
    muc_jid: string | nil
  }
  | nil
  ```

- #### `set_info(group_id, info)` {#set_info}

  Allows one to change a group's name. If `muc_jid` is specified, this function will also update the group chat's name.

  **Parameters:**

  1. `group_id: string`: Node part of the group's JID.
  2. `group_info: { name: string, muc_jid: string | nil }`

  **Returns:** `true | nil, error: string`

- #### `get_members(group_id)` {#get_members}

  Retrieves the list of members in a given group.

  **Parameters:**

  1. `group_id: string`: Node part of the group's JID.

  **Returns:** `group_members: {string}`

- #### `exists(group_id)` {#exists}

  Returns whether or not a group exists.

  **Parameters:**

  1. `group_id: string`: Node part of the group's JID.

  **Returns:** `group_exists: boolean`

- #### `get_user_groups(username)` {#get_user_groups}

  Lists which groups a given user is a part of.

  **Parameters:**

  1. `username: string`: Node part of the user's JID.

  **Returns:** `user_groups: {string}`

- #### `delete(group_id)` {#delete}

  Deletes a given group and its associated group chats.

  **Parameters:**

  1. `group_id: string`: Node part of the group's JID.

  **Returns:** `true | nil, error: string`

- #### `add_member(group_id, username, delay_update)` {#add_member}

  Adds a member to a given group, optionally delaying subscriptions until [`sync`](#sync) is called.

  ::: {.alert .alert-info}
  This function emits a [`group-user-added`](#group-user-added) event on successful execution.
  :::

  **Parameters:**

  1. `group_id: string`: Node part of the group's JID.
  2. `delay_update: boolean | nil`: Do not update subscriptions until [`sync`](#sync) is called. Defaults to `false`.

  **Returns:** `true | nil, error: string`

- #### `remove_member(group_id, username)` {#remove_member}

  Removes a member from a given group.

  ::: {.alert .alert-info}
  This function emits a [`group-user-removed`](#group-user-removed) event on successful execution.
  :::

  **Parameters:**

  1. `group_id: string`: Node part of the group's JID.
  2. `username: string`: Node part of the user's JID.

  **Returns:** `true | nil, error: string`

- #### `sync(group_id)` {#sync}

  Updates group subscriptions (used to apply pending changes from [`add_member`](#add_member)).

  **Parameters:**

  1. `group_id: string`: Node part of the group's JID.

  **Returns:** `nil`

- #### `add_group_chat(group_id, name)` {#add_group_chat}

  Creates a new group chat for a given group.

  ::: {.alert .alert-info}
  Its JID will be `<`[`util.id.short`](https://prosody.im/doc/developers/util/id)`>@<`[`option:groups_muc_host`](#configuration)`>`.
  :::

  **Parameters:**

  1. `group_id: string`: Node part of the group's JID.
  2. `name: string`: Desired name of the group chat.

  **Returns:**

  ```lua
  muc: {
    jid: string,
    name: string,
  }
  | nil, error: string
  ```

- #### `remove_group_chat(group_id, muc_id)` {#remove_group_chat}

  Removes a group chat for a given group.

  ::: {.alert .alert-info}
  This function emits a [`group-chat-removed`](#group-chat-removed) event on successful execution.
  :::

  **Parameters:**

  1. `group_id: string`: Node part of the group's JID.
  2. `muc_id: string`: Node part of the MUC JID.

  **Returns:** `true | nil, error: string`

- #### `get_group_chats(group_id)` {#get_group_chats}

  Lists group chats associated to a given group.

  ::: {.alert .alert-warning}
  Make sure to check the `deleted` property on each chat as this function might return information about deleted chats.
  :::

  **Parameters:**

  1. `group_id: string`: Node part of the group's JID.

  **Returns:**

  ```lua
  group_chats: {
    {
      id: string, -- muc_id (node part of the MUC JID)
      jid: string,
      name: string,
      deleted: boolean,
    }
  }
  | nil
  ```

- #### `emit_member_events(group_id)` {#emit_member_events}

  Emits [`group-user-added`](#group-user-added) events for every member of a group.

  **Parameters:**

  1. `group_id: string`: Node part of the group's JID.

  **Returns:** `true | false, error: string`

- #### `groups()` {#groups}

  Returns info about all groups (for every `group_id` key, the value is the equivalent of calling `get_info(group_id)`).

  **Returns:**

  ```lua
  groups: {
    <group_id>: {
      name: string,
      muc_jid: string | nil
    }
  }
  ```

  (Where `<group_id>` is a

### Emitted events {#events}

- #### `group-user-added` {#group-user-added}

  Emitted on successful [`add_member`](#add_member) and on [`emit_member_events`](#emit_member_events).

  **Payload structure:**

  ```lua
  {
    id: string, -- group_id (node part of the group's JID)
    user: string, -- username (node part of the user's JID)
    host: string, -- <module.host>
    group_info: {
      name: string,
      muc_jid: string | nil,
      mucs: {string} | nil,
    },
  }
  ```

- #### `group-user-removed` {#group-user-removed}

  Emitted on successful [`remove_member`](#remove_member).

  **Payload structure:**

  ```lua
  {
    id: string, -- group_id (node part of the group's JID)
    user: string, -- username (node part of the user's JID)
    host: string, -- <module.host>
    group_info: {
      name: string,
      muc_jid: string | nil,
      mucs: {string} | nil,
    },
  }
  ```

- #### `group-chat-added` {#group-chat-added}

  Emitted on successful [`add_group_chat`](#add_group_chat).

  **Payload structure:**

  ```lua
  {
    group_id: string,
    group_info: {
      name: string,
      mucs: {string},
    },
    muc: {
      jid: string,
      name: string,
    },
  }
  ```

- #### `group-chat-removed` {#group-chat-removed}

  Emitted on successful [`remove_group_chat`](#remove_group_chat).

  **Payload structure:**

  ```lua
  {
    group_id: string, -- group_id (node part of the group's JID)
    group_info: {
      name: string,
      mucs: {string},
    },
    muc: {
      id: string, -- muc_id (node part of the MUC JID)
      jid: string,
    },
  }
  ```

[`mod_groups`]: https://prosody.im/doc/modules/mod_groups "mod_groups – Prosody IM"