From d3e8aa670f5a896608f4b74a409d2cb9faccdb72 Mon Sep 17 00:00:00 2001 From: Eric Eastwood Date: Tue, 11 Apr 2023 13:12:06 -0500 Subject: [PATCH] Better wording on Gitter alternative --- proposals/3991-increase-power-level.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/proposals/3991-increase-power-level.md b/proposals/3991-increase-power-level.md index b4a469d3..2bd18ba5 100644 --- a/proposals/3991-increase-power-level.md +++ b/proposals/3991-increase-power-level.md @@ -97,14 +97,14 @@ the intro/context paragraphs above though. --- -As an [alternative that could solve the Gitter specific +As an alternative that could solve the [Gitter specific case](https://gitlab.com/gitterHQ/gitter.im/-/issues/4) where a user with a power level of `90` appears as "Moderator" when it actually functions as an admin role; this could be solved by spec'ing out how to figure out what is the admin PL and what is the moderator PL. Hardcoding random integers to labels just doesn't work well. For example, with the [Nheko](https://github.com/Nheko-Reborn/nheko) client, it considers people with -the permission to change powerlevels to be admins and users with redaction permissions -are moderators. Or maybe something more flexible like [MSC3949: Power Level +the permission to change power levels to be admins and users with redaction permissions +as moderators. Or maybe something more flexible like [MSC3949: Power Level Tags](https://github.com/matrix-org/matrix-spec-proposals/pull/3949). This MSC does make sense on top of those kind of changes in any case though.