-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Serverside validation for m.room.power_levels event. (SYN-120) #1237
Comments
Jira watchers: @NegativeMjark @ara4n |
Taken from "Matrix Internal".
Possibly due differences between Leo's perl client and the web client? We should probably have better C2S and S2S validation for the event content. |
Can we shoot this in the head for the next version bump? |
Having a power level being a string instead of an int makes the
|
Indeed same error:
Could be fixed easily by the built-in Python: |
7 years gone by |
@avdb13 what makes you think it can't be smaller than -1? The spec says integers can be between -9007199254740991 and 9007199254740991 https://spec.matrix.org/v1.2/appendices/#canonical-json |
@aaronraimist everything lower than |
Why would be so? If muted is -5000, default is -1000, admin is -250, superadmin is 0, then ir works just the same. (Levels are not good idea in my opinion either since I cannot have people allowed to kick but not to change topic, then other people allowed to change topic but not to kick, but that's what we have now.) |
Exactly. It has an effect if you want it to have an effect.
Synapse implements the Matrix spec. If you want to change how power levels work, you would have to change it in the spec, for example matrix-org/matrix-spec-proposals#2812.
It doesn't.
That's not true. You can set the power level required to do those things to different values. https://spec.matrix.org/v1.2/client-server-api/#mroompower_levels |
Serverside validation for m.room.power_levels events as they an unholy mix of integers and strings in some channels
(Imported from https://matrix.org/jira/browse/SYN-120)
(Reported by @ara4n)
The text was updated successfully, but these errors were encountered: