From 25e3602bbe0f76285f75abd4277959ee8add4948 Mon Sep 17 00:00:00 2001 From: Luca Becker Date: Sat, 3 Aug 2019 09:15:32 +0200 Subject: [PATCH] 3rd draft of MSC2209 --- .../2209-auth-rules-other-keys-in-m.room.power.levels.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/proposals/2209-auth-rules-other-keys-in-m.room.power.levels.md b/proposals/2209-auth-rules-other-keys-in-m.room.power.levels.md index db4d9bee..594c0b99 100644 --- a/proposals/2209-auth-rules-other-keys-in-m.room.power.levels.md +++ b/proposals/2209-auth-rules-other-keys-in-m.room.power.levels.md @@ -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