• shininghero@kbin.social
    link
    fedilink
    arrow-up
    11
    arrow-down
    1
    ·
    1 year ago

    For those who want to preemptively block hexbear ahead of defederation, it’s fairly easy to do.

    Go to /d/hexbear.net, and then click the block button in the domain section. That will add it to the domain block list on your profile.

    For desktop, it should be on the right hand side. On mobile, I had to scroll down and tap on the dotted triangle icon.

    • ekky43@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      8
      ·
      edit-2
      1 year ago

      That’d be nice, especially since it is a functionality that has been requested quite a lot recently.

      Sadly when I go to /d/hexbear.net , it gives me a 404?

      Even when using sh.itjust.works (because I’m 100% sure that I can see this post and comment section, and comment here) I seem to get the 404.

      Any idea why that might be? I imagine I’m doing it wrong.

      EDIT: It’s because you’re on Kbin, and I’m on Lemmy, isn’t it? Damnit.

    • cacheson@kbin.social
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      1 year ago

      This doesn’t block posts from hexbear, it blocks post that link to hexbear. At least in theory. In practice it’s buggy, and will just block stuff at random, so you shouldn’t use it. Also, hexbear hasn’t federated kbin, so we don’t see their posts anyway.

        • cacheson@kbin.social
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          That’s weird. I see from your profile that chapotraphouse is federating. Or at least, some of the posts are?

          We’re not on their list of allowed instances, so I assumed that meant we don’t federate at all. I guess it must just be one-sided, where we can see their posts, but they can’t see ours?