MSC3907: Mute Policy Recommendation #3907
Conversation
Fixing this typo helps make sure that when we replace all MSC placeholders with MSCXXXX where XXXX is the final IDs that this misstake doesnt persist.
Gnuxie/policy mute
FSG-Cat
changed the title
FSG-Cat
changed the title
turt2live
added
proposal
| } | ||
| ``` | ||
|
|
||
| Below is the same event but without the expiry. |
There was a problem hiding this comment.
Does it even make sense to have this without an expiry? Isn't a mute without expiry essentially a ban, or what's the reasoning?
There was a problem hiding this comment.
Yes a mute without a expiry is on the surface close to a ban but if one makes the assumption that policy application engines reverse policies that have been reversed then the assumption of it being a ban would no longer be true.
Even then a mute is in some ways not a ban since it forces you to be read only but does not eject you out of a room. Close but not equivalent and this lack of equivalence can actually end up being important for some communities.
Co-authored-by: Marcel <[email protected]>
| * is a `room` rule: | ||
| + Applied to a user: New events from the room are ignored, not displayed in notifications and | ||
| not shown to be active in a client. | ||
| + Applied to a room: No-op? Could be changing `events_default` to the same level as moderators |
There was a problem hiding this comment.
Not sure why this is a question, you cannot ban a room from a room, same with mutes.
5 participants
Rendered
MSC Co Authored by @FSG-Cat and @Gnuxie
Signed-off-by: Catalan Lover [email protected]