Matrix/synapse
Matrix/synapse
1
0
Fork 0
mirror of https://github.com/element-hq/synapse synced 2024-09-30 03:32:41 +00:00
Code Issues Projects Releases Packages Wiki Activity

deploy: a9ee832e48

Browse source
This commit is contained in:
reivilibre 2024-07-23 10:00:56 +00:00
parent edacfa724e
commit c6ff558347
4 changed files with 10 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
develop/print.html
View file

@ -4008,11 +4008,15 @@ This option replaces the previous top-level 'use_presence' option.</p>
<p>Example configuration:</p> <p>Example configuration:</p>
<pre><code class="language-yaml">presence: <pre><code class="language-yaml">presence:
enabled: false enabled: false
include_offline_users_on_sync: false
</code></pre> </code></pre>
<p><code>enabled</code> can also be set to a special value of &quot;untracked&quot; which ignores updates <p><code>enabled</code> can also be set to a special value of &quot;untracked&quot; which ignores updates
received via clients and federation, while still accepting updates from the received via clients and federation, while still accepting updates from the
<a href="usage/configuration/../../modules/index.html">module API</a>.</p> <a href="usage/configuration/../../modules/index.html">module API</a>.</p>
<p><em>The &quot;untracked&quot; option was added in Synapse 1.96.0.</em></p> <p><em>The &quot;untracked&quot; option was added in Synapse 1.96.0.</em></p>
<p>When clients perform an initial or <code>full_state</code> sync, presence results for offline users are
not included by default. Setting <code>include_offline_users_on_sync</code> to <code>true</code> will always include
offline users in the results. Defaults to false.</p>
<hr /> <hr />
<h3 id="require_auth_for_profile_requests"><a class="header" href="#require_auth_for_profile_requests"><code>require_auth_for_profile_requests</code></a></h3> <h3 id="require_auth_for_profile_requests"><a class="header" href="#require_auth_for_profile_requests"><code>require_auth_for_profile_requests</code></a></h3>
<p>Whether to require authentication to retrieve profile data (avatars, display names) of other <p>Whether to require authentication to retrieve profile data (avatars, display names) of other

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

4
develop/usage/configuration/config_documentation.html
View file

@ -348,11 +348,15 @@ This option replaces the previous top-level 'use_presence' option.</p>
<p>Example configuration:</p> <p>Example configuration:</p>
<pre><code class="language-yaml">presence: <pre><code class="language-yaml">presence:
enabled: false enabled: false
include_offline_users_on_sync: false
</code></pre> </code></pre>
<p><code>enabled</code> can also be set to a special value of &quot;untracked&quot; which ignores updates <p><code>enabled</code> can also be set to a special value of &quot;untracked&quot; which ignores updates
received via clients and federation, while still accepting updates from the received via clients and federation, while still accepting updates from the
<a href="../../modules/index.html">module API</a>.</p> <a href="../../modules/index.html">module API</a>.</p>
<p><em>The &quot;untracked&quot; option was added in Synapse 1.96.0.</em></p> <p><em>The &quot;untracked&quot; option was added in Synapse 1.96.0.</em></p>
<p>When clients perform an initial or <code>full_state</code> sync, presence results for offline users are
not included by default. Setting <code>include_offline_users_on_sync</code> to <code>true</code> will always include
offline users in the results. Defaults to false.</p>
<hr /> <hr />
<h3 id="require_auth_for_profile_requests"><a class="header" href="#require_auth_for_profile_requests"><code>require_auth_for_profile_requests</code></a></h3> <h3 id="require_auth_for_profile_requests"><a class="header" href="#require_auth_for_profile_requests"><code>require_auth_for_profile_requests</code></a></h3>
<p>Whether to require authentication to retrieve profile data (avatars, display names) of other <p>Whether to require authentication to retrieve profile data (avatars, display names) of other