One obvious next step for Meta is to implementing proprietary ActivityPub extensions that address real problems in the current spec (just as Mastodon and other implementations do).
I was about to write a comment that points out that Fediverse clients are very diverse and the way they make use of ActivityPub is also diverse, but the article makes my point for me: Threads will have specific requirements.
Of course Threads is scary. It is bigger than the Fediverse by itself. You can always shut it out if you don't like it, just like the way Mastodon-derived platforms for alt-right social media got treated. That's how you solve such problems in the Fediverse.
Comments
From the article:
One obvious next step for Meta is to implementing proprietary ActivityPub extensions that address real problems in the current spec (just as Mastodon and other implementations do).
I was about to write a comment that points out that Fediverse clients are very diverse and the way they make use of ActivityPub is also diverse, but the article makes my point for me: Threads will have specific requirements.
Of course Threads is scary. It is bigger than the Fediverse by itself. You can always shut it out if you don't like it, just like the way Mastodon-derived platforms for alt-right social media got treated. That's how you solve such problems in the Fediverse.