data.coop
/
ansible
8
3
Fork 7
Code Issues 44 Pull Requests 7 Projects 1 Releases Wiki Activity

Figure out how to monitor user reports in Matrix #162

New Issue
Open
opened 2023-05-02 19:32:49 +00:00 by samsapti · 2 comments
samsapti commented 2023-05-02 19:32:49 +00:00
Owner
Copy Link

Content cannot be reported to the homeserver admin, or at least we don't know where reports are delivered. No error occours when a report is submitted, but nothing happens on the admin-side of things. The logs indicate nothing.

Tested on element.data.coop.

EDIT: There's an API to get user reports, we need to figure out a way to monitor it.

Content cannot be reported to the homeserver admin, or at least we don't know where reports are delivered. No error occours when a report is submitted, but nothing happens on the admin-side of things. The logs indicate nothing. Tested on element.data.coop. EDIT: There's an API to get user reports, we need to figure out a way to monitor it.
samsapti added the
Existing Service
 label 2023-05-02 19:32:49 +00:00
samsapti commented 2023-05-02 19:38:31 +00:00
Author
Owner
Copy Link

Might be relevant: https://spec.matrix.org/latest/client-server-api/#reporting-content

Might be relevant: https://spec.matrix.org/latest/client-server-api/#reporting-content
samsapti commented 2023-05-02 19:41:00 +00:00
Author
Owner
Copy Link

https://matrix-org.github.io/synapse/latest/admin_api/event_reports.html

https://matrix-org.github.io/synapse/latest/admin_api/event_reports.html
samsapti changed title from Users cannot report content in Matrix to Figure out how to monitor user reports in Matrix 2023-05-02 19:50:43 +00:00
valberg added this to the Devops work project 2024-02-09 07:52:10 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
proxmox
diun
use_sudo
woodpeckerci
linting
mailman
listmonk
sshd-password
Labels
Clear labels   
Blocked

Something is blocking progress

  
Existing Service

Issues/improvements regarding existing services

  
Infrastructure Issue

Infrastructure issue that needs investigation or time to fix

  
Refactor

Refactoring of files / file structure or other improvements

  
Security Hardening

Non-verified / non-critical security improvements

  
Security Issue

Urgent security issue that needs to be fixed ASAP

  
Service Idea

Ideas for new services

  
Service Removal

Removal of services for one reason or another

  
Upgrade service
No Label
Blocked
Existing Service
Infrastructure Issue
Refactor
Security Hardening
Security Issue
Service Idea
Service Removal
Upgrade service
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Devops work
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: data.coop/ansible#162
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?