It is expected to be 2-3 months before Threads is ready to federate (see link). There will, inevitably, be five different reactions from instances:

  1. Federate regardless (mostly the toxic instances everyone else blocks)

  2. Federate with extreme caution and good preparation (some instances with the resources and remit from their users)

  3. Defederate (wait and see)

  4. Defederate with the intention of staying defederated

  5. Defederate with all Threads-federated instances too

It’s all good. Instances should do what works best for them and people should make their home with the instances that have the moderation policies they want.

In the interests of instances which choose options 2 or 3, perhaps we could start to build a pre-emptive block list for known bad actors on Threads?

I’m not on it but I think a fair few people are? And there are various commentaries which name some of the obvious offenders.

  • scarabic@lemmy.world
    link
    fedilink
    English
    arrow-up
    19
    arrow-down
    2
    ·
    2 years ago

    We need to think this through from the standpoint of an instance admin who is trying to figure out how to use Threads to make their instance grow. That’s really the only motivation I can think of to federate with Threads. Otherwise it’s just all downside. As a corporate social media entity, they are entirely opposed to everything Lemmy stands for philosophically, and their scale is a massive threat to the culture and operations of the much smaller fediverse. Why would anyone ever want to federate with them? Because they see it as an opportunity. To ride the dragon, thinking it can be controlled. This is madness. Choice 4 all the way and if it becomes necessary, 5.

    • jocanib@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      11
      arrow-down
      2
      ·
      2 years ago

      The beauty of the Fediverse is you do not need to make everyone else agree with you. It is important that mods know what you want; what you think other people should want is irrelevant.

      • scarabic@lemmy.world
        link
        fedilink
        English
        arrow-up
        11
        arrow-down
        2
        ·
        2 years ago

        No, you don’t need to go around making other people agree with you, on the fediverse or anywhere, really.

        But if you are going to enter into a mutual risk/benefit relationship with another party, it does help to understand what their motivations are, so you can figure out if they’re going to line up with your own, or lead to conflict.

        My post is about trying to understand those parties’ motivations. Not make everyone agree with me.

  • pulaskiwasright@lemmy.ml
    link
    fedilink
    English
    arrow-up
    12
    arrow-down
    1
    ·
    edit-2
    2 years ago

    4 is honestly my preference. I don’t see the need to defederate from instances that federate with Threads. But I do want to see a list of instances that federate with Threads so I can personally never comment or post there. I don’t like the idea of comments and posts I make being used to generate ad revenue for Facebook.

  • CaptObvious@lemmy.world
    link
    fedilink
    English
    arrow-up
    10
    ·
    2 years ago

    I frankly prefer options 4-5. There’s no evidence that Facebook will play nice and a lot of historical evidence that they won’t. I want to be on an instance willing to take the nuclear option if it comes to it.

  • dystop@lemmy.world
    link
    fedilink
    English
    arrow-up
    12
    arrow-down
    3
    ·
    edit-2
    2 years ago

    Everyone is talking about defederating preemptively because of XMPP and EEE. But the very fact that we know about EEE means that it’s much less likely to succeed.

    Zuck is seeing the metaverse crash and burn and he knows he needs to create the next hot new thing before even the boomers left on facebook get bored with it. Twitter crashing and burning is a perfect business opportunity, but he can’t just copy Twitter - it has to be “Twitter, but better”. So, doing what any exec does, he looks for buzzwords and trends to make his new product more exciting. Hence the fediverse.

    From Meta’s standpoint, they don’t need the Fediverse. Meta operates at a vastly different scale. Mastodon took 7 years to reach ~10M users - Threads did that in a day or two. My guess is that Zuck is riding on the Fediverse buzzword. I’m sure whatever integration he builds in future will be limited.

    TL;DR below:

  • Nine@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    1
    ·
    edit-2
    2 years ago

    So why is it important to not federate (or block) with Thread? Asking seriously. I read the article and while those are valid and real concerns. What is the net gain of that action? How does it help the fediverse? I cant see any way that it helps and lots of ways it hurts. At this point it seems like a lot of what ifs.

    Edit:

    If you need the reasons why to block Threads (meta) I think the answers below explain it better than most!

  • 0x4E4F@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    2 years ago
    1. Make your own instance, defederate from everyone, make 20 accounts, disable account registration, post from 2 or 3 accounts, upvote from the rest and make conversations.

    /j on the 5… cuz it’s a bit extreme.

  • DankMemeMachine@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    ·
    2 years ago

    I hate to say it but we already need a better Twitter and Reddit alternative than what the fediverse has to offer, then. Each time a big company comes in, the communities will get thrown into disarray, eat eachother, and generally make the original ‘vision’ of the fediverse smaller and smaller. People will use what is easy, not what is best for their interests (at least for the vast majority). The solution is still open source, community managed and driven content, but it doesn’t look like the fediverse is a long-term answer.

  • lunaticneko@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 years ago

    5, except fully neutral-ground instances (private ones used as personal access points or government instances for example)

  • vtez44@kbin.social
    link
    fedilink
    arrow-up
    0
    ·
    2 years ago

    Only real threats of Threads federation are EEE and server overload. Not the people from there or privacy. If someone wants to see some content you don’t want to see, like some opinion you don’t like, they should be able to see it. I don’t understand why there would be such list, it would be pure censorship and waste of time. I have heard Threads has a pretty good moderation, so that solves this problem anyway.

    I don’t get what would defederating with Facebook-federated instances gives you, though.

    • monerobull@monero.town
      link
      fedilink
      arrow-up
      0
      ·
      2 years ago

      I don’t get what would defederating with Facebook-federated instances gives you, though.

      Means the instance isn’t part of the hive mind and we obviously can’t have that!

      • Flax@feddit.uk
        link
        fedilink
        arrow-up
        0
        arrow-down
        1
        ·
        2 years ago

        I am a fediverse enthusiast and I am excited for Threads federating. I hope it incentivises Tumblr to federate also and then we actually finally have proper choice.

        • Kerrigor@kbin.social
          link
          fedilink
          arrow-up
          0
          ·
          2 years ago

          I see you’re not familiar with EEE. This is a classic move by enterprise to kill an open competitor.

          • Flax@feddit.uk
            link
            fedilink
            arrow-up
            0
            arrow-down
            1
            ·
            2 years ago

            I am. How could they kill the fediverse? If they tried to kill it, it would only return to how things was. Chances are tumblr could join in and then they couldn’t easily extinguish it.

            • Kerrigor@kbin.social
              link
              fedilink
              arrow-up
              0
              ·
              2 years ago

              Ever heard of XMPP?

              If a single party participating in an open standard is large enough, they can go off the track, and then kill off interoperability.

              • Flax@feddit.uk
                link
                fedilink
                arrow-up
                0
                arrow-down
                1
                ·
                2 years ago

                But this isn’t a single party. Mastodon and Lemmy and Kbin are well established

  • Bradamir@kbin.social
    link
    fedilink
    arrow-up
    0
    ·
    2 years ago

    I don’t get this platform. I’m about to just give up on social media altogether.

    I just want to know about new games and whatever else that interests me. Why’s that so hard.

    • simple@kbin.social
      link
      fedilink
      arrow-up
      0
      arrow-down
      2
      ·
      2 years ago

      You really don’t need to care about whatever’s happening with Threads as a casual user

      • artisanrox@kbin.social
        link
        fedilink
        arrow-up
        0
        arrow-down
        1
        ·
        2 years ago

        You do need to care as a casual about data miners that would love to sell your info to health insurance companies and crackhead conspiracy theorists.

  • Flax@feddit.uk
    link
    fedilink
    English
    arrow-up
    0
    arrow-down
    1
    ·
    edit-2
    2 years ago

    5 is an absolutely horrible idea.

    1 and 2 are best