kaslo/synapse
1
0
Fork 0
Code Packages Releases 124 Wiki Activity

deploy: 3f37bd6277

Browse Source
This commit is contained in:
devonh
2025-08-11 17:12:34 +00:00
parent c79a1425b8
commit 2d192d0d23
6 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
v1.135/print.html
View File

@@ -1860,7 +1860,7 @@ v1.61.0.</p>
<tr><td>v1.85.0 – v1.91.2</td><td>v1.83.0</td></tr>
<tr><td>v1.92.0 – v1.97.0</td><td>v1.90.0</td></tr>
<tr><td>v1.98.0 – v1.105.0</td><td>v1.96.0</td></tr>
<tr><td>v1.105.1 – v1.134.0</td><td>v1.100.0</td></tr>
<tr><td>v1.105.1 – v1.135.0</td><td>v1.100.0</td></tr>
</tbody></table>
<h2 id="upgrading-from-a-very-old-version"><a class="header" href="#upgrading-from-a-very-old-version">Upgrading from a very old version</a></h2>
<p>You need to read all of the upgrade notes for each version between your current
@@ -7358,7 +7358,7 @@ Setting this to a high value allows users to report content quickly, possibly in
&quot;m.room.history_visibility&quot;: 100
&quot;m.room.canonical_alias&quot;: 50
&quot;m.room.avatar&quot;: 50
&quot;m.room.tombstone&quot;: 100
&quot;m.room.tombstone&quot;: 100 (150 if MSC4289 is used)
&quot;m.room.server_acl&quot;: 100
&quot;m.room.encryption&quot;: 100
</code></pre>

2
v1.135/schema/synapse-config.schema.json
View File

@@ -4218,7 +4218,7 @@
},
"default_power_level_content_override": {
"type": "object",
"description": "The `default_power_level_content_override` option controls the default power levels for rooms.\n\nUseful if you know that your users need special permissions in rooms that they create (e.g. to send particular types of state events without needing an elevated power level). This takes the same shape as the `power_level_content_override` parameter in the /createRoom API, but is applied before that parameter.\n\nNote that each key provided inside a preset (for example `events` in the example below) will overwrite all existing defaults inside that key. So in Example #1, newly-created private_chat rooms will have no rules for any event types except `com.example.foo`.\n\nThe default power levels for each preset are:\n\n```yaml\n\"m.room.name\": 50\n\"m.room.power_levels\": 100\n\"m.room.history_visibility\": 100\n\"m.room.canonical_alias\": 50\n\"m.room.avatar\": 50\n\"m.room.tombstone\": 100\n\"m.room.server_acl\": 100\n\"m.room.encryption\": 100\n```\n\nIn Example #2 the default power-levels for a preset are maintained, but the power level for a new key is set.",
"description": "The `default_power_level_content_override` option controls the default power levels for rooms.\n\nUseful if you know that your users need special permissions in rooms that they create (e.g. to send particular types of state events without needing an elevated power level). This takes the same shape as the `power_level_content_override` parameter in the /createRoom API, but is applied before that parameter.\n\nNote that each key provided inside a preset (for example `events` in the example below) will overwrite all existing defaults inside that key. So in Example #1, newly-created private_chat rooms will have no rules for any event types except `com.example.foo`.\n\nThe default power levels for each preset are:\n\n```yaml\n\"m.room.name\": 50\n\"m.room.power_levels\": 100\n\"m.room.history_visibility\": 100\n\"m.room.canonical_alias\": 50\n\"m.room.avatar\": 50\n\"m.room.tombstone\": 100 (150 if MSC4289 is used)\n\"m.room.server_acl\": 100\n\"m.room.encryption\": 100\n```\n\nIn Example #2 the default power-levels for a preset are maintained, but the power level for a new key is set.",
"default": {},
"examples": [
{

2
v1.135/searchindex.js
View File

File diff suppressed because one or more lines are too long

2
v1.135/searchindex.json
View File

File diff suppressed because one or more lines are too long

2
v1.135/upgrade.html
View File

@@ -267,7 +267,7 @@ v1.61.0.</p>
<tr><td>v1.85.0 – v1.91.2</td><td>v1.83.0</td></tr>
<tr><td>v1.92.0 – v1.97.0</td><td>v1.90.0</td></tr>
<tr><td>v1.98.0 – v1.105.0</td><td>v1.96.0</td></tr>
<tr><td>v1.105.1 – v1.134.0</td><td>v1.100.0</td></tr>
<tr><td>v1.105.1 – v1.135.0</td><td>v1.100.0</td></tr>
</tbody></table>
<h2 id="upgrading-from-a-very-old-version"><a class="header" href="#upgrading-from-a-very-old-version">Upgrading from a very old version</a></h2>
<p>You need to read all of the upgrade notes for each version between your current

2
v1.135/usage/configuration/config_documentation.html
View File

@@ -3642,7 +3642,7 @@ Setting this to a high value allows users to report content quickly, possibly in
&quot;m.room.history_visibility&quot;: 100
&quot;m.room.canonical_alias&quot;: 50
&quot;m.room.avatar&quot;: 50
&quot;m.room.tombstone&quot;: 100
&quot;m.room.tombstone&quot;: 100 (150 if MSC4289 is used)
&quot;m.room.server_acl&quot;: 100
&quot;m.room.encryption&quot;: 100
</code></pre>