Shutdown room API should avoid generating notifications

[t3chguy]

The shutdown room API can cause useless notifications since the homeserver is going to be mass kicking all users anyway.

---

Moved from element-hq/element-web#6996

[anoadragon453]

Sorry, what does the "mute the room" actually mean?

I'm not sure what this issue is asking for.

[t3chguy]

Pinging @ara4n for more info

[H-Shay]

This is 30 days old with no updates and seems to come from a 2-year-old issue in element-web, so unless anyone strongly disagrees I am going to close this issue.

[t3chguy]

Keep in mind this is a feature request from @ara4n

[t3chguy]

Presumably mute in this context is to set the permissions required to speak out of bounds of local users

[H-Shay]

I'll reopen no problem.

[clokep]

I've attempted to clarify this issue a bit -- as is mentioned in the Element Web issue I'm not sure what could be done over federation here, but it seems like something useful could be done for local users.

[richvdh]

Hum; I'm still not sure we're clear what this issue is actually asking for.

Presumably mute in this context is to set the permissions required to speak out of bounds of local users

This doesn't sound like notifications - rather it's about setting the power levels in the room so that users can't send messages in the first place. I think the problem is that kicking can take a long time, so people can still send messages while it's going on, which isn't terribly helpful.

[clokep]

Presumably mute in this context is to set the permissions required to speak out of bounds of local users

This doesn't sound like notifications - rather it's about setting the power levels in the room so that users can't send messages in the first place. I think the problem is that kicking can take a long time, so people can still send messages while it's going on, which isn't terribly helpful.

That's a possible interpretation of the original request too. This sounds like #11842, which is fixed.

[DMRobertson]

Closing as a duplicate of #11842. If @ara4n had something specific in mind that wasn't covered by this, a new issue is very welcome.