• Tiger Jerusalem@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 year ago

    People keep parroting that Threads will kill us all but won’t explain how it could happen to the fediverse. As in, actual steps. Because Flipboard federated and I’m not flooded with news posts. Mastodon is used for Nazi instances and I’m not flooded by Nazi content, even if the maintainer don’t block that particular instace due to not knowing it exists.

    No, XMP is not a valid example. It requires specific people to be on that specific platform for you to connect with them, like iMessage and WhatsApp. The fediverse is nothing like that.

    Can someone explain exactly how EEE will happen? Technically? Other than FUD?

    EDIT: thank you all for the replies, there’s definitely some good points that are worth considering that I couldn’t find elsewhere.

    • bitwolf@lemmy.one
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Here’s an example I can see happening.

      Threads will want to implement post reactions to maintain parity with Facebook. Threads expands the ActivityPub spec to include reactions.

      Now, every other instance will not be compatible with reactions. Users complain they cannot see reactions.

      Admins have two choices now:

      • Refuse to implement reactions because they are not part of the spec. Users leave and join threads.

      • ActivityPub adds reactions to the standard, all instances must now support reactions. Meta has now started dictating the spec.

      I feel the XMP fears do have some sentiment, and it’s really a matter of how the broad username interprets these issues (including the Thread users which would be family and friends).

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

        I don’t think so. There are tons of ActivityPub implementations out there already that don’t even support all parts of the official spec (Lemmy can’t display attached images, for example). There are also implementations that have tacked on additional functionality beyond the official spec (again, Lemmy’s downvotes).

        It’s a very flexible protocol that allows developers to pick and choose what features they want to implement in their services.