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
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.
Oh, be assured that threads will one day defederate and build a wall so you can’t access their content anymore. The Fediverse need to have a critical mass of users to survive when it happens, but if the features threads offers are too compelling and the majority of the new accounts are made in there then the Fediverse is screwed.
Isn’t that already the case? The Fediverse is doing fine under current circumstances.
so youve confirmed that i have nothing to fear from this. thank you
i will be calling this the ‘feature envy’ argument henceforth
for profit company that enabled genocide is problem
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.