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

  • Kierunkowy74@kbin.social
    1·
    11 months ago

    For example, Threads supports audio posts, a feature not currently supported within ActivityPub(…)

    Laughs in Funkwhale, Castopod, and even any ActivityPub platform implementing an Audio object type

    Wired checked no Meta claim against reality.

  • haui@lemmy.giftedmc.comEnglish
    1·
    11 months ago

    I keep seeing people hating on the EEE crowd. Finally meta makes a move that proves we were right.

  • originalucifer@moist.catsweat.com
    1·
    11 months ago

    i guess ill say it again. meta hasnt modified the protocol, and the bells and whistles they feed their own users on their own instance means nothing to the rest of the 'verse. calm the fuck down

  • Blaze@discuss.onlineEnglish
    0·
    11 months ago

    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.

    Here we go