I just saw that lemmy.ml has pre-emptively defederated from threads. Are there any plans to do that here? I personally want nothing to do with Meta/Facebook, and I’m sure that’s not an unpopular opinion around here.

edit: y’all, please pay attention to where you are when coming from all.

edit again: kbin really ought to make a post’s home instance more clear.

    • CeledielOP
      link
      fedilink
      101 year ago

      Ultimately, I will support the decision of our gracious host, whose time and money has made this instance possible. But I do not care to interact at all with Threads/Meta and I do not believe their presence on the fediverse is anything other than an attempt to either monetize it or potentially make it obsolete

      Agreed, 100%. And thanks for putting it more eloquently than I was able to, haha!

    • Treevan 🇦🇺
      link
      fedilink
      91 year ago

      There was the theory behind some EU laws that by joining the Fediverse, they get around some monopoly issues.

      So possibly 3 things that are most likely.

    • CrazyEddie041
      link
      fedilink
      5
      edit-2
      1 year ago

      I will support the decision of our gracious host, whose time and money has made this instance possible.

      I mean… he’s a developer, not a deity. I appreciate that this is a space he made, and he can do what he wants. But I’m also free to leave if he decides to federate with a Zuckerberg product.

      • CeledielOP
        link
        fedilink
        11
        edit-2
        1 year ago

        Not trying to be rude or anything, but you’re not even here. This isn’t kbin. This is a specific meta community for this instance, slrpnk.net.

        • CrazyEddie041
          link
          fedilink
          101 year ago

          That’s, uh… that’s a good point you got there. I still get confused by the whole federation thing lol

          • CeledielOP
            link
            fedilink
            71 year ago

            I went and found this thread on kbin.social, and I’m gonna put the blame squarely on them. It was extremely unclear that this thread was on another instance, and really the only way I was able to tell was by looking at the URL.