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

  • originalucifer@moist.catsweat.com
    0·
    9 months ago

    Ha… no.

    As I said before, their instance and it’s bells and whistles are irrelevant to my instance. Me and my instance only care about The ap protocol. I have no reason to fear their instance as long as it’s pumping out the standard protocol. Anything not standard gets dropped.

    Zero problem here.

      • originalucifer@moist.catsweat.com
        0·
        9 months ago

        ahh i see the ‘non-technical, moral’ argument. i can appreciate this one. take a stand, you do you!

        im going to do me.

        i dont go out of my way to block instances just because i hate the companies. im focusing on interoperability concerns.

        im glad we can agree, theres no technical concern with threads federation.