Moderation page improvements and remove deprecated /delete_room synapse api #1462
Conversation
ghost
mentioned this pull request
There was a problem hiding this comment.
Thanks for updating it! This guide is now severely outdated and will require a nearly completely rewrite.
In the meantime your changes are welcome. I left suggestions to point to more up to date APIs from the spec website. Please review and apply, and we can merge this in :)
Co-authored-by: Thibault Martin <[email protected]>
Co-authored-by: Thibault Martin <[email protected]>
Co-authored-by: Thibault Martin <[email protected]>
Co-authored-by: Thibault Martin <[email protected]>
ghost
requested a review
from 
|
@thibaultamartin Is the delete room api curl request command correct? |
I believe it is, is there anything that makes you think it's not? |
|
@thibaultamartin Thanks for answering. No, it's just that I've never used curl to send Matrix commands before. |
|
Thanks for helping with the docs :) |
| curl 'https://matrix.org/_synapse/admin/v1/shutdown_room/!roomid:matrix.org' \ | ||
| -H "Authorization: Bearer $token" -XPOST \ | ||
| curl 'https://matrix.org/_synapse/admin/v2/rooms/!roomid:matrix.org' \ | ||
| -H "Authorization: Bearer $token" -X DELETE \ | ||
| -d'{"new_room_user_id": "@abuse:matrix.org", "message": "This room has been removed from the matrix.org homeserver due to violating the terms of use.", "room_name": "Room unavailable"}' |
There was a problem hiding this comment.
@uranuspucksaxophone I think you need to add block: true here for this to be equivalent to the shutdown_room API. Otherwise you are just deleting it but not disallowing people from joining in the future.
Closes #1281
I renamed the file, does that affect anything?Edit: Seems to work well on the netlify preview.
Preview: https://pr1462--matrix-org-previews.netlify.app