[wp-meta] [Making WordPress.org] #6834: Support Forums: Require a reason when flagging a user
Making WordPress.org
noreply at wordpress.org
Thu Mar 9 17:46:08 UTC 2023
#6834: Support Forums: Require a reason when flagging a user
----------------------------+-----------------------
Reporter: Clorith | Owner: (none)
Type: enhancement | Status: reopened
Priority: normal | Milestone:
Component: Support Forums | Resolution:
Keywords: |
----------------------------+-----------------------
Comment (by Ipstenu):
I say this constantly: Asking the volunteer mods to do MORE work results
in FEWER mods and MORE mistakes.
Also I want to caution: **TELLING someone they got mod-looked for calling
people names rarely, if ever, works out well.** Seriously few people in
the history of ever have taken that well. It's like how asking someone to
calm down never works.
I would recommend a different kind of user-note or a form that lets
people:
1. Flag a user _or ban them_ as a dropdown
2. Pick a general option of WHY flagged (bad language/spammy
links/dogpiling on a review/etc) from a dropdown (if OTHER, then it's free
form)
3. Write in a detailed Mod note as to why. Include the stuff like the
history, exactly what was said and to whom, etc. This may require some NON
PUBLIC info (like IPs and emails) so for privacy protection, it might be
different.
That would then email a sanitized version of the situation and now we
don't have to worry about mods being followed home. No need to reply in
public. Just:
> Your reply/post [subject of thread] was removed for [reason from option
2] and your account has been flagged for moderation.
>
> This means [explain what modlook means].
>
> If you have questions/concerns please come to the #forums channel in
slack...
>
> The original content of your comment is included below:
> [original comment]
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/6834#comment:12>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list