From 4adc33d520744afb6dc922cab34c6a6f81b977e6 Mon Sep 17 00:00:00 2001 From: clokep Date: Fri, 17 Nov 2023 13:44:41 +0000 Subject: deploy: c4f5522189687c1e739d63246b5a6668d89b2d5f --- latest/modules/presence_router_callbacks.html | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) (limited to 'latest/modules/presence_router_callbacks.html') diff --git a/latest/modules/presence_router_callbacks.html b/latest/modules/presence_router_callbacks.html index c8d26631a1..1574797c03 100644 --- a/latest/modules/presence_router_callbacks.html +++ b/latest/modules/presence_router_callbacks.html @@ -76,7 +76,7 @@ @@ -147,9 +147,15 @@

Presence router callbacks

-

Presence router callbacks allow module developers to specify additional users (local or remote) -to receive certain presence updates from local users. Presence router callbacks can be -registered using the module API's register_presence_router_callbacks method.

+

Presence router callbacks allow module developers to define additional users +which receive presence updates from local users. The additional users +can be local or remote.

+

For example, it could be used to direct all of @alice:example.com (a local user)'s +presence updates to @bob:matrix.org (a remote user), even though they don't share a +room. (Note that those presence updates might not make it to @bob:matrix.org's client +unless a similar presence router is running on that homeserver.)

+

Presence router callbacks can be registered using the module API's +register_presence_router_callbacks method.

Callbacks

The available presence router callbacks are:

get_users_for_states

-- cgit 1.4.1