Probably wise to block this community. This ain’t the first time this has happened. I’d suggest leaving for your own good.

  • jordanlund@lemmy.world
    link
    fedilink
    arrow-up
    68
    ·
    9 months ago

    So… it’s complicated…

    I’m not a mod here, but the lemmy.world admins have set me up with some tools and bots to take care of trouble makers.

    So the reports never made it to me because I’m not a mod.

    A bot got the reports showing the offensive subject and a button for “Perma Ban” and it looked (to me) like the Perma Ban had already been enabled.

    It now looks like it wasn’t. :(

    So this post was brought to the attention of an Admin chat that I’m part of, I ran down the post manually and hit it with the ban-hammer bot as well as going back through the bot posts and making sure the Perma Ban option was triggered.

    HOPEFULLY it’s gone now. The user should be permanently banned as well.

      • jordanlund@lemmy.world
        link
        fedilink
        arrow-up
        36
        ·
        9 months ago

        Because while I am a lemmy.world mod, I’m not a mod for lemmyshitpost.

        I see all the reports for Politics and World News and a few other TINY communities (hello Comic Books!) but I wouldn’t ordinarily see the reports for lemmyshitpost.

        That’s where the bot comes in. Multiple reports happening really quickly get reported to Discord and then all of us can go “Whoah, what’s going on?”

        If we click the link and it’s legit bad, there’s a Perma Ban button that any of us can use even if we aren’t a mod on that community.

        In my case, I clicked the link in Discord and the post didn’t load and I was like “Cool! Already done! One less thing to worry about!”

        But that wasn’t because it was resolved, it was because I had blocked lemmyshitpost from my personal feed. :(

        I realized what had happened when I saw the discussion this morning, ran down the post and used all the bots to unleash hell. ;)

    • Mario_Dies.wav@lemmy.dbzer0.comOP
      link
      fedilink
      arrow-up
      15
      arrow-down
      5
      ·
      9 months ago

      Seems to not be a problem on most instances

      See you on the flipside. I’m not putting myself at risk over a shitposting community

      • Ghostalmedia@lemmy.world
        link
        fedilink
        English
        arrow-up
        20
        ·
        9 months ago

        It’s because certain instances and communities are popular and bigger targets.

        All Lemmy instances have the same janky mod tools that don’t adequately alert mods. The cracks show when the communities get bigger.

      • can@sh.itjust.works
        link
        fedilink
        arrow-up
        9
        ·
        9 months ago

        I think they just target the largest communities, and many happen to be hosted on lemmy.world

      • db2@lemmy.world
        link
        fedilink
        arrow-up
        5
        ·
        9 months ago

        The problem isn’t the community, it’s the instances with quick no-checks signups that they can create an account on in seconds, they don’t care if the account gets nuked because they can spend another 1.3 seconds making another. They can post in any community.

  • Ghostalmedia@lemmy.world
    link
    fedilink
    English
    arrow-up
    22
    ·
    9 months ago

    Mod of a larger community here (which is still small compared to Reddit).

    The mod tools for Lemmy aren’t great. For example, Lemmy doesn’t have the ability to send separate high priority notifications for reports.

    All in all, your mods need help. Volunteer to moderate so we have more eyeballs, and continue to make noise about Lemmy needing better tools. You can block if you want, but that doesn’t address the core problem.

  • Mac@programming.dev
    link
    fedilink
    arrow-up
    8
    ·
    edit-2
    9 months ago

    It was removed from the source instance already (lemmy.world)

    Not sure why lemmy.dbzer0 doesnt get that federated

    • Mario_Dies.wav@lemmy.dbzer0.comOP
      link
      fedilink
      arrow-up
      4
      arrow-down
      10
      ·
      9 months ago

      It’s not like this is the first time this has happened. It’s still grossly negligent to not have figured that part out.

      • can@sh.itjust.works
        link
        fedilink
        arrow-up
        7
        ·
        9 months ago

        I don’t blame you for not looking again. I’m not a mod in this community but I’ve forwarded this post to the appropriate channels just in case.

        • Mario_Dies.wav@lemmy.dbzer0.comOP
          link
          fedilink
          arrow-up
          11
          arrow-down
          2
          ·
          9 months ago

          Yeah, I reported it six hours ago, and it had already been up for three hours at that time.

          I genuinely thought they’d have removed it and didn’t expect to see it again.

          Even if it’s a federation issue, this is inexcusable. They need to get their shit together, but I’m not sticking around for that to happen.