• PrettyFlyForAFatGuy@lemmy.ml
    link
    fedilink
    arrow-up
    16
    arrow-down
    1
    ·
    edit-2
    1 year ago

    i’ve said it before and i’ll say it again. give me a spec and i’ll (try to) write you a tool.

    i’m a competent coder, but i have no idea kind of what mod tools are needed.

    • 7heo@lemmy.ml
      link
      fedilink
      arrow-up
      10
      ·
      edit-2
      1 year ago

      For starters, a way to unban people would be nice. Then, also, a way to easily see new content for their community. Like, only new content. And not see it after it has been marked as “reviewed” (except as context to unreviewed content, when unfolded). I mean, new posts, new comments, etc. With alerts. Also, sudden activity alert.

      A way to match keywords, and bring up matching posts and comments.

      Metrics about each user’s contributions to the community, are they new, or seasoned. Did they contribute mostly popular content or unpopular content? What words do they use most? Etc.

      Compiling multiple reports for a single post/comment into one. Ignoring reports from select users.

      That’s all I can think of for now.

      But, essentially, a dashboard with live content, showing “old” content as “greyed out”, and relevant actions, would be really, really useful.

      Edit: additionally, automated actions would be great. Answering posts/comments matching regexes with templates populated with the user’s information; automatically removing, issuing warnings, and banning (outright or after n warnings) people for specific terms, etc.

      It would also really help to have automation workflows (e.g. user commented with “r-word” or “n-word”, autocomment a warning, wait X minutes/hours, or Y minutes/hours after user comments again, remove comment/ban).

      This automation could come as an additional tool, to be ran under a separate account.

    • Terevos@lemm.ee
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      1 year ago
      1. Report queue. Right now, reports go to a queue that both instance owners and mods use. This makes it impossible to mod because the instance owners mark items as completed before mods even had a chance to look at them.

      Now, if it’s the case where it’s user abuse it’s fine for the instance owner to take care of it.

      But if it’s just breaking the rule of a community, the instance owner should never even see it.

      Separating the queues would help both mods and instance owners.

      1. The ability to hide a community from All and/or Local. Some communities just aren’t appealing to the general public. And when All surfers see posts, they just downvote them into oblivion.
      • PrettyFlyForAFatGuy@lemmy.ml
        link
        fedilink
        arrow-up
        0
        arrow-down
        1
        ·
        1 year ago

        these could be a little more difficult. they seem to be instance level features.

        i might be able to do a tool for the first one using filters if there is a way to insert keywords into a report e.g. “To Mods” or “To Admins”