mirrors/synapse
1
0
Fork 0
mirror of https://github.com/element-hq/synapse.git synced 2024-12-14 11:57:44 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 3

deploy: d2eab22de7

Browse source
This commit is contained in:
clokep 2023-10-20 15:41:28 +00:00
parent 4020b71ce3
commit 5b489ff452
4 changed files with 20 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
develop/modules/presence_router_callbacks.html
View file

@ -147,9 +147,15 @@
</div>
<h1 id="presence-router-callbacks"><a class="header" href="#presence-router-callbacks">Presence router callbacks</a></h1>
<p>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 <code>register_presence_router_callbacks</code> method.</p>
<p>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.</p>
<p>For example, it could be used to direct all of <code>@alice:example.com</code> (a local user)'s
presence updates to <code>@bob:matrix.org</code> (a remote user), even though they don't share a
room. (Note that those presence updates might not make it to <code>@bob:matrix.org</code>'s client
unless a similar presence router is running on that homeserver.)</p>
<p>Presence router callbacks can be registered using the module API's
<code>register_presence_router_callbacks</code> method.</p>
<h2 id="callbacks"><a class="header" href="#callbacks">Callbacks</a></h2>
<p>The available presence router callbacks are:</p>
<h3 id="get_users_for_states"><a class="header" href="#get_users_for_states"><code>get_users_for_states</code></a></h3>

12
develop/print.html
View file

@ -10517,9 +10517,15 @@ class EventCensorer:
return event_dict
</code></pre>
<div style="break-before: page; page-break-before: always;"></div><h1 id="presence-router-callbacks"><a class="header" href="#presence-router-callbacks">Presence router callbacks</a></h1>
<p>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 <code>register_presence_router_callbacks</code> method.</p>
<p>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.</p>
<p>For example, it could be used to direct all of <code>@alice:example.com</code> (a local user)'s
presence updates to <code>@bob:matrix.org</code> (a remote user), even though they don't share a
room. (Note that those presence updates might not make it to <code>@bob:matrix.org</code>'s client
unless a similar presence router is running on that homeserver.)</p>
<p>Presence router callbacks can be registered using the module API's
<code>register_presence_router_callbacks</code> method.</p>
<h2 id="callbacks-2"><a class="header" href="#callbacks-2">Callbacks</a></h2>
<p>The available presence router callbacks are:</p>
<h3 id="get_users_for_states"><a class="header" href="#get_users_for_states"><code>get_users_for_states</code></a></h3>

2
develop/searchindex.js
View file

File diff suppressed because one or more lines are too long

2
develop/searchindex.json
View file

File diff suppressed because one or more lines are too long