Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Moderation page improvements and remove deprecated /delete_room synapse api #1462

Merged
merged 8 commits into from Oct 18, 2022
Merged

Moderation page improvements and remove deprecated /delete_room synapse api #1462

Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
008bcca
Rename 2019-04-29-moderation.mdx to moderation-guide.mdx
Sep 26, 2022
40aefc9
Mention latest spec version
Sep 26, 2022
e2302fd
Change the synapse old /delete_room API to the new /DELETE API
Sep 26, 2022
3c6790b
Update gatsby/content/docs/moderation-guide.mdx
Oct 5, 2022
b1f69b2
Update gatsby/content/docs/moderation-guide.mdx
Oct 5, 2022
431b825
Update gatsby/content/docs/moderation-guide.mdx
Oct 5, 2022
18d0922
Update gatsby/content/docs/moderation-guide.mdx
Oct 5, 2022
1467e68
Merge branch 'matrix-org:master' into moderation-page-improvements
Oct 5, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions ...by/content/docs/2019-04-29-moderation.mdx → gatsby/content/docs/moderation-guide.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -147,7 +147,7 @@ In the early days of Matrix we proposed the concept of ‘active application ser

* Support for bulk redactions (looping over individual redactions is a viable workaround however)
* Ability for room moderators to delete content from the media repository when redacting the event which refers to it. (this can be improved in future)
* UI for setting server ACLs ([https://github.com/vector-im/Element-web/issues/7084](https://github.com/vector-im/Element-web/issues/7084))
* UI for setting server ACLs ([https://github.com/vector-im/element-web/issues/7084](https://github.com/vector-im/element-web/issues/7084))


### Moderation tooling
Expand Down Expand Up @@ -190,12 +190,12 @@ If you're using Element, when you go to view more information about a particular
![Element-deactivate-btn](/docs/projects/images/moderation8.png)


Removing abusive rooms is done by calling the /shutdown_room API, e.g:
Removing abusive rooms is done by calling the delete room API, e.g:


```
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"}'
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed by #1524

```

Expand Down Expand Up @@ -253,9 +253,9 @@ Synapse does not currently provide tools to block connections by IP - instead we

Synapse supports a module-like system which can be used to block servers from doing certain actions, such as sending invites to your users. [t2bot/synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam) is one example of how this works - see the code for a bit more information on what is possible. Although this won't prevent servers from interacting with your server, it can help with reducing the amount of spam/malicious content.

“Defederating” your server from another server is currently done on a room by room basis - either using server ACLs if you have control of the room in question, or by using the /shutdown_room API if you do not.
“Defederating” your server from another server is currently done on a room by room basis - either using server ACLs if you have control of the room in question, or by using the /DELETE API if you do not.

In future, this may be refined to let servers automatically implement /shutdown_room semantics on any room which matches a given pattern (e.g. whose room admins are on a given server).
In future, this may be refined to let servers automatically implement delete room API semantics on any room which matches a given pattern (e.g. whose room admins are on a given server).


### Moderating the room directory
Expand All @@ -264,7 +264,7 @@ Each Matrix server maintains a publicly viewable directory of rooms. By default

The server admin can limit which users are allowed to publish rooms to the public room directory via the `room_list_publication_rules` config option in Synapse.

The server admin can moderate the directory by delisting rooms by calling the /directory/list/room API with visibility: private ([https://matrix.org/docs/spec/client_server/r0.4.0.html#put-matrix-client-r0-directory-list-room-roomid](https://matrix.org/docs/spec/client_server/r0.4.0.html#put-matrix-client-r0-directory-list-room-roomid)).
The server admin can moderate the directory by delisting rooms by calling the [`/directory/list/room/{roomId}` API](https://spec.matrix.org/latest/client-server-api/#put_matrixclientv3directorylistroomroomid) with `visibility: private`).


### Moderating room aliases
Expand All @@ -275,7 +275,7 @@ By default, any user can create room aliases, which can be an abuse vector - par

The server admin can limit which users are allowed to create room aliases via the `alias_creation_rules` config option in Synapse.

The server admin can moderate the aliases that exist on their server by calling the /directory/room API with DELETE: ([https://matrix.org/docs/spec/client_server/r0.4.0.html#delete-matrix-client-r0-directory-room-roomalias](https://matrix.org/docs/spec/client_server/r0.4.0.html#delete-matrix-client-r0-directory-room-roomalias)).
The server admin can moderate the aliases that exist on their server by calling the [room API](https://spec.matrix.org/latest/client-server-api/#delete_matrixclientv3directoryroomroomalias).

Element/Web also exposes the ability to delete a room alias from the Room Directory view as an easter egg for server administrators - shift-clicking on the entry in the Room Directory will call the above API to remove the alias and the room from the directory.

Expand Down