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
Add logging to the bot. Let admins choose a chat to output logs for the bot, and configure what actions that should be logged.
This can help admins ensure that there's no brigading on users and, with anonymous suggestions enabled, prevent repeat offenders from posting fake/trolling suggestions.
The text was updated successfully, but these errors were encountered:
Okay cool, can certainly consider it or atleast what it might look like.
Noting that our stance on anonymous suggestions/actions is that to an end user/guild they are truly anonymous unless by exception. In terms of dealing with that without needing to involve us, we have these commands to combat issues.
I do like this idea! I originally planned to implement this in the original v3 version and even wrote some code) around it. @Skelmis, you can review that for some ideas on how this might play out.
For commands such as /suggest, where the anonymous option is set to True, logged messages could be parsed correctly to omit relevant information. So, regardless of what's logged, admins would not be able to see the author of an anonymous suggestion.
But I do like this idea, and it is something Ethan and I can further discuss regarding the semantics of a logging system.
Here are some examples of how logged messages looked:
Add logging to the bot. Let admins choose a chat to output logs for the bot, and configure what actions that should be logged.
This can help admins ensure that there's no brigading on users and, with anonymous suggestions enabled, prevent repeat offenders from posting fake/trolling suggestions.
The text was updated successfully, but these errors were encountered: