Threads is automatically hiding comments that mention Pixelfed - eviltoast

For anyone wondering if Threads and Facebook at large will be a fine neighbor in the space and compatible with other apps/services in the fediverse: they’re already automatically hiding comments that mention Pixelfed https://mastodon.social/@dansup/112126250737482807

  • techt@lemmy.world
    link
    fedilink
    English
    arrow-up
    20
    arrow-down
    1
    ·
    8 months ago

    This is a strange response for me because de-federating is an active step on behalf of its admin, usually after a vote amongst its users, at creating a virtual boundary between the two entities. How is that burying your head in the sand? And yeah, lemmy.world is big, but aside from the obvious loss of content/users, what other effect will that have on the mass of de-federated instances?

    • just another dev@lemmy.my-box.dev
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      2
      ·
      edit-2
      8 months ago

      Someone correct me if I’m wrong, but my understanding is that since LW will federate with them, any content they host, will end up on meta.

      For example, this discussion we’re having right now is on !technology@lemmy.world. So it doesn’t matter whether our own instances have defederated meta - our posts and comments here will bring them value. Directly, in the form of content. And indirectly, in the form of processable data for machine learning, shadow profiles, etc.

      • SorteKanin@feddit.dk
        link
        fedilink
        English
        arrow-up
        14
        ·
        8 months ago

        but my understanding is that since LW will federate with them, any content they host, will end up on meta

        Your understanding is wrong. Instances don’t forward stuff from other instances to other instances. Instances only send their own content directly to the instances they federate with.