We spoke with a product manager at Meta to learn how the company plans to bring interoperability to Threads in the coming months. It faces both technical and cultural challenges.

Meta is treading carefully, doing a phased implementation while continuing conversations with Fediverse leaders. This will give the company more time to iron out some of the integration kinks. “Do we adapt the protocol to be able to support this?” Lambert asks. “Or do we try to do some kind of interesting, unique implementation?” For example, Threads supports audio posts, a feature not currently supported within ActivityPub, so Meta is experimenting with “federating” a text transcription of the original post instead of the audio version.

It was never a good idea federating with Threads

  • nicetriangle@kbin.social
    1·
    9 months ago

    Funny thing is that the mainstream threads audience would probably do more harm to the mastodon ecosystem by orders of magnitude.

    There is a big cultural disconnect. I’m active in both and they are very different communities by and large.

    • Dame @lemmy.mlEnglish
      1·
      9 months ago

      This is an odd take and not even close. It is in fact the Fediverse that would be more harmful. Meta has laws and government scrutiny. There’s a lot of willing filth on the Fediverse. Blocking instances more so became a think the last 1-2 years. Blocking those instances does not mean they don’t exist. Can you find harmful content on Meta’s platform? Sure but that’s mostly due to volume. Where as there’s Fediverse instances straight up for illegal and gross content