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

  • Blaze@discuss.onlineEnglish
    263·
    10 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

      • originalucifer@moist.catsweat.com
        116·
        10 months ago

        they modified AP already? wow that was quick. i was under this crazy impression they were using text in a field designed for text. silly me!

        • ZeroHora@lemmy.mlEnglish
          14·
          10 months ago

          No the next step is saying that text transcription didn’t worked like they wanted so we need to change the AP to allow what the majority wants(spoiler: they are the majority)

            • ZeroHora@lemmy.mlEnglish
              3·
              10 months ago

              I’m just joking, I don’t think they can make a change unilaterally easily.

                • Diabolo96@lemmy.dbzer0.comEnglish
                  81·
                  10 months ago

                  It’s far worse. They’re making improvements only on their side. The protocol everyone uses will lack the features their protocol offers. In other words, their side of the garden is now greener than ours, and one day, their side will be so majestic and beautiful compared to ours that almost nobody will want to visit it anymore, and like a flame without fuel, the Fediverse will Extinguish on its own.

                  • originalucifer@moist.catsweat.com
                    53·
                    10 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
                12·
                9 months ago

                right this is the ‘feature envy’ argument

                ha a blog post, ok. even the blog post admits it

                While XMPP still exist and is a very active community

                every instance of xmpp folded to google because it “got most of user base to migrate”

                if the fediverse cant actually compete content and feature wise across 10s of thousands of very different services/experiences built on AP, (unlike XMPP), we deserve to die.

                the world is a different place than it was . how many people do you know use gtalk? zero? its zero. xmpp? STILL A THING YOU CAN USE. google didnt kill shit. the market at the time seriously minimized its use, cuz everyone was lazy and not running their own server-server products.

                back today.

                do you have any evidence of Meta modifying the AP protocol? can you point at their actual ability to modify the protocol? can you tell me how an instance that drops all nonstandard AP traffic is going to suffer from Meta attempting it?