You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Discord audit log isn't really useful to us. It would be beneficial to surface in #mod-log when:
A user is banned
A user is kicked
A message is deleted
Here's the current mod log format:
<@tag> (username) warned 1 times:
00 minutes ago in <#channelId> <action taken>, by modName: https://discord.com/channels/id/id/id on 01/31/2023, 11:59 PM GMT+00
> lorem ipsum dolar sit amet
An MVP of this could be a simple listener on the audit log event, firing off a specific reportUser() type.
As a stretch goal, I think it could be valuable to abstract this into some variety of system for overseeing and managing external oversight of mod actions. I think this could be a valuable product for businesses looking to track anomalies in community spaces as part of a detection program.
The text was updated successfully, but these errors were encountered:
Discord audit log isn't really useful to us. It would be beneficial to surface in
#mod-log
when:Here's the current mod log format:
An MVP of this could be a simple listener on the audit log event, firing off a specific
reportUser()
type.As a stretch goal, I think it could be valuable to abstract this into some variety of system for overseeing and managing external oversight of mod actions. I think this could be a valuable product for businesses looking to track anomalies in community spaces as part of a detection program.
The text was updated successfully, but these errors were encountered: