As a moderator, I sometimes come across posts which I consider problematic, but which I would not like to take action on myself, given a prior history of personal conflict with the respective person. Usually, I would like to just flag the post in this case, but this sadly autohides it, defeating that purpose.
Except for sending a message to my fellow mods manually, is there anything suitable for this situation?
I don’t think so. I’d say the easiest way to handle this would be to use whispers to quietly @mention the other moderators.
One way I can think of is to impersonate a test TL0/TL1 user to flag the post. Though this might be a little lengthy.
I wonder if you could then use a theme component to add a button in the flag modal to go to the test user’s admin page to impersonate them, using something like Custom Components -- add button or text at any plugin outlet.
I don’t think all flag types immediately hide posts. I think you can safely use “something else,” or you could create a custom flag.
if you think it is “problematic” then flag it with the appropriate flag type and let another moderator judge for themselves, then choose to un-hide it if they disagree. This is the proper workflow of the review queue and Discourse moderation in general. When you say “prior history of personal conflict with respective person”, I assume you mean that your judgement as a moderator may be affected, and thus you should act as a regular user would and flag it accordingly. as stated, the other alternative to use are whisper posts that other staff can see, or since you said this only happens “sometimes” simply:
I have here and there been trying to create a Theme component code to check flag against both the flagged member and the member who flagged the post against the moderator. If the moderator is the flagged post owner or the user who flagged the post. It would hide the review buttons except say defer.
I have attempted to use AI but suspect the recent changes to the flag review menu may lbe causing some issues
This would be handy as well with Category moderators to ensure imho integrity in moderation actions. As in the past had a moderator who would flag posts of a member they had a disagreement then agree with their own flag
.while some would say choose your moderators better. Having a simple method to prevent temptation is best
Now a TC might not be overly secure the AU code suggested I could have the component generate a log if someone were to circumvent. Maybe late will share sample code in a Dev post
I don’t quite understand how your attempts to create a component that hides something in the review queue help prevent the post from being hidden due to a flag by a moderator. Flags by users with high trust levels sometimes have more power than intended. @Steradiant is not the first who wishes for a flag that doesn’t hide the post Trigger Moderator Attention Instead of Auto-hiding Flag
Then I maybe haven’t explained it sufficiently for you to understand the purpose
The idea is quite simple if the Nod reviewing the Review Que is directly involved with the flagged content. Then the only option is to defer for another not involved moderator to review the flagged content.
So
mlMod = Author if Post that is flagged. They cannot resolve the flag as they are the author of the flagged content. For integrity another mid needs to review it
Mod is the user that flagged the post. They cannot resolve the flag as it is also a conflict as they flagged the post. So another Mod needs to review and resolve flag.
This ensures integrity of the Moderation process by having safe guards against biased moderation in my case a fellow mod would flag and resolve the flags he inflicted in other users during difference of opinions that had nothing to do with “Arguing with a mod”.
While we can imolent policies and rely on choosing the right ppl to be on a team. A safe guard prevention is best to remove temptations. Plus with adding category moderation this safeguard also protects mod integrity with volunteers.
This simple idea helps with moderation neutrality.