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.

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

Audit Log #565

Open
Beyley opened this issue Jul 19, 2024 · 0 comments
Open

Audit Log #565

Beyley opened this issue Jul 19, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@Beyley
Copy link
Member

Beyley commented Jul 19, 2024

Refresh should store an audit log of all moderation actions, so bans, level deletions, metadata changes by admins/curators, etc. into a viewable log accessible through the API. There should also be discord webhook integration so that these actions can be automatically logged to a discord channel aswell.

This is useful for admins so that there is a consolidated place to keep track of past actions taken against a particular user, but could also be useful for server owners, who may want to make this viewable through a public discord channel, to make the gameserver moderation more transparent.

@Beyley Beyley added enhancement New feature or request proposal A proposal for a feature that is not a missing feature from the game labels Jul 19, 2024
@jvyden jvyden removed the proposal A proposal for a feature that is not a missing feature from the game label Jul 19, 2024
jvyden added a commit that referenced this issue Aug 24, 2024
Rough port from DO code to integrate AI image scanning into Refresh.
This should help reduce the photo endpoint abuse we've been seeing from
DT, while using the same existing infrastructure that works incredibly
well.

This does not scan every uploaded texture as this would increase server
load significantly. It will only scan under certain circumstances:
- for uploaded photos
- for images uploaded via the API

This also brings in the option to automatically restrict users who
upload images with banned tags if configured. This will be left off on
production while I gauge if this is going to false-flag for normal
non-abuse activity.

Oh, this also introduces support for a staff-only webhook. This could be
used for a non-persisted audit log if we wanted to use that as a
solution for #565.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants