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
Removal reason for moderators is covered by mod_note and mod_reason_title on the submission/comment
Filter reason (automod)
Getting automod filter reason requires access to modlog or is retrievable from mod notes under action.details for the first automoderator entry.
Neither approach lends itself to good api usage at this point...
Mod log usage is not implemented in CM yet and would require all existing bots to re-authenticate to ask for modlog oauth scope. However this would probably be a better approach long-term as we can cache mod log much easier than mod notes.
Mod notes is more direct and is already implemented but will require an additional api call to get the reason.
It would also depend on context...for instance getting filtered reason for a new activity just received from unmoderated means an api call either way since modlog is stale and we don't have mod notes for the user. Additionally, getting filtered reason for old activities would be easier done with mod notes as we can't easily determine how many pages of mod log would need to be fetched before we find the activity id.
The text was updated successfully, but these errors were encountered:
Removal by Mods
Removal reason for moderators is covered by
mod_note
andmod_reason_title
on the submission/commentFilter reason (automod)
Getting automod filter reason requires access to modlog or is retrievable from mod notes under
action.details
for the first automoderator entry.Neither approach lends itself to good api usage at this point...
Mod log usage is not implemented in CM yet and would require all existing bots to re-authenticate to ask for modlog oauth scope. However this would probably be a better approach long-term as we can cache mod log much easier than mod notes.
Mod notes is more direct and is already implemented but will require an additional api call to get the reason.
It would also depend on context...for instance getting filtered reason for a new activity just received from
unmoderated
means an api call either way since modlog is stale and we don't have mod notes for the user. Additionally, getting filtered reason for old activities would be easier done with mod notes as we can't easily determine how many pages of mod log would need to be fetched before we find the activity id.The text was updated successfully, but these errors were encountered: