The Fediverse is currently divided over whether or not to block Threads. Here are some of the things people are worried about, some opportunities that might come from it, and what we need to do to prepare.

  • davel [he/him]@lemmy.ml
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    2
    ·
    11 months ago

    we’d just defederate them.

    It’s true that we can always choose to defederate from them. What’s to worry about is their meddling with the ActivityPub standard using their incomparably vast resources, and them making their own extensions to the standard in efforts to suck users back into the Borg. Things like that.

    Unfortunately, even if instance admins were to unanimously defederate, Meta—or any social media corporation—could create white-label instances to take their place, and we might be none the wiser of their control of them.

    • Sean Tilley@lemmy.mlOPM
      link
      fedilink
      English
      arrow-up
      2
      ·
      11 months ago

      Unfortunately, even if instance admins were to unanimously defederate, Meta—or any social media corporation—could create white-label instances to take their place, and we might be none the wiser of their control of them.

      I don’t necessarily disagree with this idea, but they would have to justify the business case to their shareholders. As of right now, the idea of a whitelabel personal silo is a limited value proposition to people not already invested in the Fediverse. If it’s whitelabel, what will Meta do? Start a new company? Inevitably, people would figure it out, and go with something else.

      It’s true that we can always choose to defederate from them. What’s to worry about is their meddling with the ActivityPub standard using their incomparably vast resources, and them making their own extensions to the standard in efforts to suck users back into the Borg. Things like that.

      I said this a little further up in the conversation, but if Meta produces some horrendous, awful version of ActivityPub that only benefits them, what’s stopping the rest of us from forking the protocol or adopting a different one? If we never switch to their version of doing things, and there’s feature breakage between us and Meta, who actually loses here?

      • davel [he/him]@lemmy.ml
        link
        fedilink
        English
        arrow-up
        2
        ·
        11 months ago

        If it’s whitelabel, what will Meta do? Start a new company? Inevitably, people would figure it out, and go with something else.

        I think what’s more likely to happen than my maximalist argument, is that some existing instances will get direct or indirect funding or other forms of support from Meta, and start influencing their direction.

    • originalucifer@moist.catsweat.com
      link
      fedilink
      arrow-up
      4
      arrow-down
      2
      ·
      11 months ago

      right, just like the extended SMTP and now we are beholden to metas magnificent SMTP implementation that has extinguished all others.

      pffft. the protocol can only be extended by consortium… thats where your worry should lie. everything ive read says they have no chance bustin into that circle.

      so all thats left is 'but geez their users will get this bell and that whistle that other instances wont… yep. exactly as the 'verse intended. get off your fuckin ass and innovate. give those users a reason to not want an @threads account not based on pure fucking spite.