wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

3rd draft of MSC2209

Browse source
This commit is contained in:
Luca Becker 2019-08-03 09:15:32 +02:00 • committed by GitHub
parent 42dbeee7d3
commit 25e3602bbe
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
proposals/2209-auth-rules-other-keys-in-m.room.power.levels.md
View file

@ -19,7 +19,7 @@ The auth rules regarding `m.room.power_levels` have been established in room
version 1. The general idea here was that creators of a new `m.room.power_levels`
event are only able to make changes to something that is equal to or lower than
their own power level.
So, assuming a room with Alice (50), Bob(100), `m.room.power_levels` at 50,
So, assuming a room with Alice (50), Bob (100), `m.room.power_levels` at 50,
`m.room.name` at 75 and `m.room.topic` at 25 would mean the following:
* Alice CAN alter `m.room.topic` to any power level up to her own, in this case 50
@ -51,8 +51,8 @@ So the rule [10.d](https://matrix.org/docs/spec/rooms/v1.html) of the auth rules
room version 1 would be updated in a new room version to:
For each entry being added, changed or removed in events, users __and notifications__
keys:
> For each entry being added, changed or removed in events, users __and notifications__
>keys:
## Tradeoffs