Modlog, which includes a site ban—something only admins can do.

The community bans also include communities that aren’t moderated by any instance admins, and some that are only moderated by a single person who likely isn’t aware of actions taken under their community’s name.

  • Draconic NEO@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    2
    ·
    13 days ago

    Honestly it’s not really a good way of doing it in my opinion, seems like it could potentially spam a lot of ban messages if a user interacted with a lot of communities. Would be better if they worked on federating site bans with every community, and also federating the message in the global modlog instead of mod banned user do mod banned user from lemmy.domain.tld or whatever the instance domain is. That way information is still communicated and you don’t get problems with them being able to interact in communities on a server they were banned from. All while not spamming the modlog.

      • Draconic NEO@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        13 days ago

        I’m hoping they implement federation of site bans, I’ve seen a lot of people banned from the site the community is hosted on still replying and pushing their disgusting rhetoric in comments of posts and it still continues to be federated because they don’t get blocked from those communities from a site ban.

        • Home bans federate everywhere.
          Remote bans don’t, which makes sense, because otherwise lemmygrad could ban your sjw account which makes no sense.
          That’s kinda how they go to the workaround of banning from every community in that instance.
          But then .world is still running an old version that doesn’t do that anyway

          • Draconic NEO@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            2
            ·
            12 days ago

            Yeah that’s true. I meant more that they’d carry a copy of the site ban record in all the communities hosted by that instance and federate that even when you’re a remote user, it would treat it the same as a community ban from all communities on that instance but only be a single entry and most importantly would apply to every community on that instance.

            The way they do it now is great but as it is the flaw is that they can participate in communities they never participated in before, which can be taken advantage of by malicious users in the same way as the old method where they weren’t given community bans at all.