Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

event reports get lost in a database table #4007

Closed
CHANist opened this issue Oct 5, 2018 · 2 comments
Closed

event reports get lost in a database table #4007

CHANist opened this issue Oct 5, 2018 · 2 comments
Labels
z-p2 (Deprecated Label)

Comments

@CHANist
Copy link

CHANist commented Oct 5, 2018

In Client Server API r0.4.0, I found that client can report any inappropriate event to server admins, but in synapse, what it does, seems to store it to the database, and do nothing else.
I think that a better approach is to create a single room and puts all server admins into this room, and when there are any inappropriate events client sent to the server, it would push to this room, specifying who send the request, the roomId and the inappropriate eventId. So that server admin can have a look at the events. And if it is inappropriate, server admins will have the right to delete the message, or even deactivate the user.

@neilisfragile neilisfragile added z-p2 (Deprecated Label) enhancement labels Oct 5, 2018
@richvdh richvdh changed the title Request for implementation of Client Reporting an inappropriate Event to Server Admin(s) event reports get lost in a database table Jan 6, 2020
@richvdh
Copy link
Member

richvdh commented Jan 6, 2020

for the record: the reports go into event_reports.

@anoadragon453
Copy link
Member

anoadragon453 commented Sep 22, 2020

I think we can close this now that #8217 is a thing.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
z-p2 (Deprecated Label)
Projects
None yet
Development

No branches or pull requests

4 participants