Lemmy.zip admin
Contact me via hello@lemmy.zip


  • Elsewhere: me.lemmy.zip - See my accounts across the internet
  • 2 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle



  • Most other social networks allow users to select whether they are reporting a violation of community rules, or site rules as whole.

    Why not take this approach to simplify it then?

    Asking the user to specify who they think should receive a report feels like it will add confusion (not to mention is subjective anyway), and could create delays in responding to important stuff if the user picks the “wrong” option. If a user picks the mod option on csam report then it might get missed by an admin? At least the option between “this community” or “site rules” is a bit clearer.

    This is to prevent cases of admins accidentally preventing mods from moderating according to their own community rules

    As an admin I should be able to respond to a mod report on a community if I’m there first and its urgent, i.e. csam. This is a policy/discussion point between mods and admins on any given instance and shouldn’t be enforced in the software. Separation for clarity’s sake is fine, I even encourage that as I don’t tend to touch a report for a community anyway as it stands, but I should be able to mark a report complete if I have dealt with it. Otherwise I’m just going to go to the post and sort it out anyway, so its just adding complexity.

    Admins can still always explicitly take over communities by making themselves mods, in this way, they are able to handle mod reports for any abandoned communities, etc

    Barriers/extra steps to administration is not the way forward here. Continuing with Admins being able to mark reports resolved just makes sense.

    Alternatively, we could make reporting even more granular. It would be possible to allow users to select only a specific instances admins as the intended report audience, for example.

    No. This is a step backwards in transparency and moderation efforts. Granularity and more options is not always a good thing. If you’ve ever had the misfortune of using Meta’s report functionality you’ll know how overly complex and frustrating their report system is to use with all their “granularity”.

    Simplicity of use and getting a report to someone who can do something about it quickly should always be the priority, adding options and functionality should be secondary and support this. If you don’t want to be stepping on moderators toes, make that clear in your guidelines and processes.

    I am legally on the hook for content on my instance, not the moderators, and proposing changes that make it harder to be an admin is a touch annoying.

    To add: I would suggest thinking about expanding this to notify the user a report has been dealt with/resolved, optionally including rationale, because that feedback element can sometimes be lacking.