Give users a possibility to force-leave a room, no matter how corrupt the room is

[ilu33]

Steps to reproduce

4 persons are in an old room that was once bridged to hackint.org (no idea whether that matters). The room fell prey to spammers with highly illegal material. We cleaned up as best we could, but the room does still exist. Ca. 10 of those spammers could not be kicked. We want to kick all the spammers and leave the room so that it will disappear after the waiting period.
Everything else works as expected (just well known bugs). The only fix we need is to get rid of the room.
Please help, the room really really needs to disappear.

Outcome

No matter whether in element-web/desktop/android, every action results in this type of error
MatrixError: [500] Internal server error (https:///_matrix/client/v3/rooms/!fVEOllFrPdYBngbVTy%3Airc.hackint.org/leave)
Browser console:
rageshake.ts:74 Kick error: M_UNKNOWN: MatrixError: [500] Internal server error (https://<homeserver>/_matrix/client/v3/rooms/!fVEOllFrPdYBngbVTy%3Airc.hackint.org/kick) e.<computed> @ rageshake.ts:74 (anonymous) @ logger.ts:94 (anonymous) @ UserInfo.tsx:708 Promise.then (async) onClick @ UserInfo.tsx:701 async function (async) onClick @ UserInfo.tsx:694 ze @ react-dom.production.min.js:52 We @ react-dom.production.min.js:52 (anonymous) @ react-dom.production.min.js:53 Fr @ react-dom.production.min.js:100 Rr @ react-dom.production.min.js:101 (anonymous) @ react-dom.production.min.js:113 Me @ react-dom.production.min.js:292 (anonymous) @ react-dom.production.min.js:50 Nr @ react-dom.production.min.js:105 Qt @ react-dom.production.min.js:75 Xt @ react-dom.production.min.js:74 t.unstable_runWithPriority @ scheduler.production.min.js:18 Ki @ react-dom.production.min.js:122 Ae @ react-dom.production.min.js:292 Yt @ react-dom.production.min.js:73 fetch.ts:60 POST https://<homeserver>/_matrix/client/v3/rooms/!fVEOllFrPdYBngbVTy%3Airc.hackint.org/leave 500 (Internal Server Error) fetch @ fetch.ts:60 requestOtherUrl @ fetch.ts:304 request @ fetch.ts:241 authedRequest @ fetch.ts:159 membershipChange @ client.ts:5599 leave @ client.ts:5474 a @ client.ts:5509 leaveRoomChain @ client.ts:5520 T @ leave-behaviour.ts:112 async function (async) T @ leave-behaviour.ts:71 onFinished @ MatrixChat.tsx:1246 (anonymous) @ Modal.tsx:213 (anonymous) @ QuestionDialog.tsx:54 ze @ react-dom.production.min.js:52 We @ react-dom.production.min.js:52 (anonymous) @ react-dom.production.min.js:53 Fr @ react-dom.production.min.js:100 Rr @ react-dom.production.min.js:101 (anonymous) @ react-dom.production.min.js:113 Me @ react-dom.production.min.js:292 (anonymous) @ react-dom.production.min.js:50 Nr @ react-dom.production.min.js:105 Qt @ react-dom.production.min.js:75 Xt @ react-dom.production.min.js:74 t.unstable_runWithPriority @ scheduler.production.min.js:18 Ki @ react-dom.production.min.js:122 Ae @ react-dom.production.min.js:292 Yt @ react-dom.production.min.js:73

Operating system

Linux, but all others too

Application version

Element: 1.11.52 Crypto version: Olm 3.2.15

How did you install the app?

Elements repo

Homeserver

private homeserver, synapse, recently update d (not sure where users can see the version?)

Will you send logs?

No

[t3chguy]

No matter whether in element-web/desktop/android, every action results in this type of error MatrixError: [500] Internal server error

As is clear from this, it is not an Element issue. I suggest seeking help from the maintainers of the server software which you are running.

[ilu33]

I understand. But still a user should be able to force-leave a room - as long as the spam is there, the only way the user could avoid to seriously incriminate himself would be to deactivate the account and leave matrix altogether? That would be sad. No matter our problem, but there must be a way to avoid getting prosecuted because you can't leave a room. Immediately and without help from the server admin. This is really serious and can ruin lives. Having this kind of spam even if only in your cache means "1 year minimum" in my jurisdiction, no matter how or why it got there.

I changed this to an enhancement request, please reopen. @t3chguy

[t3chguy]

But still a user should be able to force-leave a room - as long as the spam is there, the only way the user could avoid to seriously incriminate himself would be to deactivate the account and leave matrix altogether?

What is a client meant to do if the server isn't behaving to spec? The endpoints aren't working and are erroring with 500 ISEs.

MatrixError: [500] Internal server error (https:///_matrix/client/v3/rooms/!fVEOllFrPdYBngbVTy%3Airc.hackint.org/leave) the client is instructing the server to have your user leave the room, this action is failing. The client cannot do anything else.