bottom text

  • CriticalResist8A
    link
    fedilink
    arrow-up
    16
    ·
    2 years ago

    Huh. It’s a pretty dead instance though (pardon the pun) but since they claim to be “poggerinos”, which is in our blocklist, I can block them too. Not much lost anyway.

    • Fiona (she/her)🏳️‍⚧️
      link
      fedilink
      arrow-up
      7
      ·
      2 years ago

      I think one instance’s linked list does not have to match with another’s blocked list

      So we can allow beehaw, and they can ban us, and that means there’s no federation

        • CriticalResist8A
          link
          fedilink
          arrow-up
          9
          ·
          2 years ago

          Yep, this list is automatically updated and the page exists on every lemmy instance – the software installs it by default. Now that I blocked this instance you will see the page updated automatically with it in the blocklist.

          Defederating, or the blocklist, is unilateral. We only block instances that do nothing against spam or are fascist. Don’t have any other reason to block tbh.

          Since beehaw blocks us, we and they won’t see each other’s content, but we can still meet in “neutral ground”, i.e. third-party instances that we both federate with. I’m not entirely sure if it works different, I think if one instance puts you in the blocklist it’s enough that you will never see each other.

          The reason they block us is because they are anticommunist 🤐 They thought, when they set up beehaw, that we took up too much space on their server and that was one reason given for not federating. Then they found out it was a bug with log files (lemmygrad doesn’t take 80 gigs of space lol).

          Now I’m also seeing a lot of overlap between beehaw, sopuli and perthchat (possibly other instances as well, such as midwest.social and mander.xyz) – they share mods and users. If I didn’t know any better I’d say they’re concerting with each other to form a bloc of sorts. But that’s also just the nature of federation.

          • Arsen6331 ☭
            link
            fedilink
            arrow-up
            5
            ·
            2 years ago

            Oh, the log files got them. I’ve had many stories of multi-gigabyte-large log files breaking stuff on my servers.

            • CriticalResist8A
              link
              fedilink
              arrow-up
              5
              ·
              2 years ago

              Did lemmy.ca also defederate from us or are they just inactive? I sort of thought I’d start seeing more klanada-centric stuff when they first announced they made that instance.

              According to their instances list: https://lemmy.ca/instances, we are one of three instances they block 🤣 (one is wolfballs, the other is a Breton-language instance of all things to block).

              One more question if you don’t mind, do you guys get notified when an instance in our link list blocks us, or is it just…they’re there one day and gone the next and you’re just as surprised?

              I think it’s the latter. I’ve never got a message or anything.

              Documentation is lacking on lemmy so most of the stuff I learn through trial and error x) for example, I have no idea why I’m discovering instances that we should federate with (federation is enabled by a checkbox) but don’t.

      • nutomic@lemmy.ml
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        2 years ago

        Not true, federation blocklists are essentially one-way. Beehaw has you blocked, so they wont see any content from lemmygrad. But lemmygrad doesnt have beehaw blocked, so its content is shown here. Admins should consider blocking these instances to hide the content.

      • Arsen6331 ☭
        link
        fedilink
        arrow-up
        5
        ·
        edit-2
        2 years ago

        The way federation usually works is that a server will begin federating with another server once it encounters content from said other server. Therefore, instances on that list would’ve posted a post or comment or something on lemmygrad or on another instance seen by someone on lemmygrad, and that caused us to federate with them.

    • Arsen6331 ☭
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      2 years ago

      This is a bit complex to explain. Essentially, if someone was browsing their own instance and it was federated with an instance that was federated with us (like lemmy.ml), they would be able to see lemmygrad content. Upon encountering such content, their server would establish federation with lemmygrad automatically. Same is true for the opposite, so if someone on lemmygrad saw content from another instance, lemmygrad would federate with that instance.

      • CriticalResist8A
        link
        fedilink
        arrow-up
        4
        ·
        2 years ago

        So in simpler terms maybe, there needs to be a trigger for federation to occur. Instances don’t ping other instances automatically. The simplest trigger is to go on an instance’s post from your instance and post a comment there.

        It’s like there’s no radar and you need to actually see the plane in the sky with your own eyes.

        Another way of encountering an instance would be if you both federate with a third instance and they post there and you see it or interact with their post I guess.