• NotSoMewwo@pawb.socialEnglish
      1·
      3 months ago

      For full context: The mod abuse was a incident between sirsquid (Liam/GamingOnLinux) and ‘go $fsck yourself’ (the person that comments this on every linking to GamingOnLinux.com). The alleged mod abuse is Liam deleting a post by ‘go $fsck yourself’ criticizing the title on one of his articles. Liam later stepped down as moderator.

      Was Liam being a childish? Yeah. Is there a reason why ‘go $fsck yourself’ is being vague about what the mod abuse actually was and to what extent? Probably.

      Incident was at 2024 May 22 Mod Log: https://lemmy.ml/modlog/15063 Screenshot Incident Thread: https://lemmy.ml/post/15894308

      For more context, after Liam stepped down: https://lemmy.ml/post/17376889/11932442

      • go $fsck yourself@lemmy.worldEnglish
        1·
        3 months ago

        Very succinct and includes 99% of the situation. Thanks, and well done.

        Only things I would add would be: Being a moderator on lemmy and not knowing that modlogs are public is baffling. That alone really outlines the fact he was unqualified for the role.

        And that it seems pretty obvious the comments were only deleted by him to hide his own. He had already shown an inability to be measured and collected, as well as a poor understanding of the platform from a moderation perspective. Then, his clear disregard for the only rule for the community by lashing out at something that could have been more easily dismissed entirely. He should have just deleted the comment without a response. My mildly stupid comment just did not deserve that kind of reaction.

        It all serves as solid evidence that he was willing to abuse his mod role for something so minor, and a person like that wouldn’t stop there.

        The real cherry on top is how pathetic it is to go to mastodon to complain about the public mod logs on lemmy.