• CAVOK@lemmy.world
    link
    fedilink
    English
    arrow-up
    17
    ·
    5 months ago

    This community is the biggest one by far. Shutting this would be bad IMHO. Is there a way to move it to another instance?

    • Servais@dormi.zoneOP
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      2
      ·
      edit-2
      5 months ago

      I agree. This one is definitely the most active one.

      @poVoq@slrpnk.net, maybe lemm.ee can be an option? The .ee domain name suggests its’ European, and all of the communities are English-speaking.

      • Servais@dormi.zoneOP
        link
        fedilink
        English
        arrow-up
        5
        ·
        5 months ago

        You can pin a message to a new one, and lock the old one down, that works for most of the people

        • Parodper@foros.fediverso.gal
          link
          fedilink
          English
          arrow-up
          7
          ·
          5 months ago

          In that case mods should do that ASAP, to give enough time to people to notice it before the server shuts down.

          Also should probably create the new community, lemm.ee doesn’t seem to have one already.

            • Servais@dormi.zoneOP
              link
              fedilink
              English
              arrow-up
              5
              ·
              5 months ago

              Even if the server keeps running, not being able to access the frontend is a bit worrying

              • poVoq@slrpnk.netM
                link
                fedilink
                English
                arrow-up
                3
                ·
                edit-2
                5 months ago

                The community on lemmy.ml has the problem that there are some very persistent users that constantly post pro-Russian propaganda or similar mis-information to it, and the lemmy.ml admins refuse to appoint a new mod and seem to be generally fine with that. I certainly wouldn’t want to moderate a similar community where Hexbear and Lemmygrad users have full access to like they would on lemm.ee. if fact I wouldn’t even be able to as my home instance is defederated from these instances and thus such posts would be invisible to me.

                • sunaurusA
                  link
                  fedilink
                  English
                  arrow-up
                  3
                  ·
                  edit-2
                  5 months ago

                  To be honest, neither Hexbear nor Lemmygrad has caused any noticable issues for lemm.ee. I recently compiled some stats for lemm.ee rule breakers by home instance, and as you can see in this post (in the “Administration” section), neither of those instances even made the top 10.

                  In general, mods haven’t complained about those two instances either, and the stats for community bans by independent community mods are more or less very similar. If any users creates issues in a lemm.ee community, then the community mods are free to just ban those users, regardless of what instance their account is hosted on.

                  if fact I wouldn’t even be able to as my home instance is defederated from these instances and thus such posts would be invisible to me

                  Preventing such situations for lemm.ee mods is actually one of the many reasons we don’t want to use defederation as a moderation tool on lemm.ee - we rather use site bans etc. Too much collateral damage with defederation, especially when dealing with larger instances which probably have vastly more innocent users than problematic ones. We reserve defederation for more extreme cases, like spam instances & CSAM.

                • DarkThoughts@fedia.io
                  link
                  fedilink
                  arrow-up
                  2
                  ·
                  5 months ago

                  I’m not saying to move to .ml, I’m saying it still has quite too many large communities for most instances to consider defederating from them. Personally I block all .ml communities manually since kbin / mbin does not have a universal instance blocking feature.