Matrix: no way to report abuse #125

Closed
opened 2026-09-06 12:04:34 -04:00 by Salastil · 1 comment
Owner

Matrix has a reporting endpoint - POST /rooms/{roomId}/report/{eventId} with a
reason and a score - which sends a message to the homeserver's administrators. moho
has nothing: report_content does not appear in the daemon, so the only answers to
somebody behaving badly are ignoring them (#99) or leaving.

Those are the answers that work on the person. Reporting is the one that reaches
whoever runs the server, and it is the only one a moderator can act on.

What is needed

  • The report endpoint, with a reason typed by the person reporting.
  • An entry on a message's own menu, next to the moderation entries that are already
    gated by power level (components/MessageRow.tsx) - reporting needs no power at
    all, which is the point of it.
  • Room-level reporting (/rooms/{roomId}/report) where the server supports it.

Done looks like: a message can be reported to the homeserver without leaving moho.

Reference: Element.

Matrix has a reporting endpoint - `POST /rooms/{roomId}/report/{eventId}` with a reason and a score - which sends a message to the homeserver's administrators. moho has nothing: `report_content` does not appear in the daemon, so the only answers to somebody behaving badly are ignoring them (#99) or leaving. Those are the answers that work on the person. Reporting is the one that reaches whoever runs the server, and it is the only one a moderator can act on. **What is needed** - The report endpoint, with a reason typed by the person reporting. - An entry on a message's own menu, next to the moderation entries that are already gated by power level (`components/MessageRow.tsx`) - reporting needs no power at all, which is the point of it. - Room-level reporting (`/rooms/{roomId}/report`) where the server supports it. **Done looks like:** a message can be reported to the homeserver without leaving moho. Reference: Element.
Salastil added the featureprotocollow priority labels 2026-09-06 12:04:34 -04:00
Salastil removed the protocol label 2026-09-06 12:49:16 -04:00
Author
Owner

Finished — https://git.salastil.com/Salastil/nobilis/commit/5ddd786 and https://git.salastil.com/Salastil/moho/commit/8608c8d

POST /rooms/{roomId}/report/{eventId} with a reason, on the message's own menu, next to the moderation entries and deliberately not gated like them: those need power in the room and this needs none, which is the point of it.

The reason is required rather than optional — a moderator receiving "this message was reported" and nothing else knows only that somebody pressed something.

Verified as far as is decent: reporting a bogus event id comes back M_NOT_FOUND: Unable to report event, which proves the route, the auth and the body without troubling a real moderator with a test report.

Finished — https://git.salastil.com/Salastil/nobilis/commit/5ddd786 and https://git.salastil.com/Salastil/moho/commit/8608c8d `POST /rooms/{roomId}/report/{eventId}` with a reason, on the message's own menu, next to the moderation entries and deliberately not gated like them: those need power in the room and this needs none, which is the point of it. The reason is required rather than optional — a moderator receiving "this message was reported" and nothing else knows only that somebody pressed something. Verified as far as is decent: reporting a bogus event id comes back `M_NOT_FOUND: Unable to report event`, which proves the route, the auth and the body without troubling a real moderator with a test report.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Salastil/moho#125