(Reposting some stuff I posted on the crosspost source)

For as long as this article is, it is remarkably free of journalism. It is basically a press release from Meta saying that they’re planning to implement Threads in a few months, and aren’t announcing anything further at this time.

“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?”

This is a fascinating question, both in its lack of an answer, and in the inherent framing of the question that of course they’re going to introduce incompatibilities, and the discussion is simply about how to do it. I also like the use of the word “interesting.”

Mastodon allows some artistic nudity

…

Additionally, specifics are still murky regarding exactly how user data will be handled after the connections between networks are established. For example, if you federate a post from Threads and decide to delete it afterwards, what happens to the cached post on the servers of the other networks?

That… is not the central question that’s on people minds about how user data will be handled. Presumably you were in a position to ask Rachel Lambert, the product manager at Meta who started the company’s journey towards interoperability, a more obvious and salient question, and include in your article her response.

Meta is treading carefully, doing a phased implementation while continuing conversations with Fediverse leaders.

Who are these leaders and what are they saying about this? This, also, seems like it would have been pertinent information to include. If Meta’s answer was “You’re not allowed to know that,” then including that response would have made the article quite a bit more illuminating than simply pretending it didn’t occur to you to ask for any details.

Facebook is operated by a large corporation which assigns a famously low priority to the interests of its users, except insofar as they can be used to make money (which is of course Meta’s right to do, more or less). Mastodon is operated by its users themselves and designed according to how they’d like it to operate. And yet, somehow, there are these issues and shortcomings originating on the Mastodon side that Meta will have to carefully monitor to shield its users from, and that’s first and foremost on their mind throughout this entire rollout, and what they’re chiefly invested in watching as it all happens.

The actual thing, sans bullshit:

What Meta’s Fediverse Plans Mean for Threads Users by Reece Rogers

5–6 minutes

Rachel Lambert, a product manager at Meta, started her company’s journey towards interoperability by breaking Adam Mosseri’s Threads account.

In December, Meta activated a test where users could follow the head of Instagram’s Threads feed on an open-source social media platform, Mastodon. But when users tried to view Mosseri’s posts over on Mastodon, nothing showed up. Lambert’s team scrambled and contacted Mastodon engineers to resolve the technical issues.

Hiccups aside, the test was historic for Meta. From Facebook to Instagram, the company has typically walled off its apps from outside data, so interoperability on Threads is new territory for Meta employees to navigate.

“It’s always exciting to be able to take a big step like this. We’ve never decentralized one of our apps before,” Lambert says.

The social media giant plans to release more cross-network features this year. While it’s easy to get lost in the jargon of the Fediverse, ActivityPub, and other pushes toward an interoperable experience for social media, the big idea is simple. In the coming months, Threads users should gain the ability to follow accounts from other social networks and to publish posts that will appear not only in Threads but elsewhere on the social web.

The technology that makes this possible is ActivityPub. First launched in 2018, the software protocol enables cross-compatibility between niche corners of the social internet on the federated constellation of open networks collectively known as the Fediverse. These decentralized social networks have been around a while, but they were mainly populated by the most terminally online users—until the chaotic upending of Twitter under Elon Musk. The changes at X sent hordes of dissatisfied users out in search of newer, more welcoming homes for their memes and shitposts. Many landed in the Fediverse.

When Meta dropped Threads last summer, Mosseri emphatically promised to decentralize its feeds eventually. But building the mechanisms that allow Threads to plug into a collection of independent networks, even using an agreed-upon standard like ActivityPub, is a delicate undertaking if you’re a giant company like Meta. “We’re kind of like the big whale that’s coming into this conversation,” Lambert says. Some Fediverse administrators worry that Threads’ interoperability plans, coupled with Meta’s institutional prowess, could overpower the more diminutive alcoves on the decentralized internet.

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?” Instead of the audio for voice posts, Meta considered federating text transcripts, but ultimately decided to stick with sharing the audio.

Lambert hesitates to put an exact timeline on the rollout of ActivityPub support, but she says general users may be able to access the new features in a couple of months. Access will first arrive for Threads accounts open to the public, and the activation process will be opt-in. “We have some milestones that we’re working towards,” Lambert says. “But I think we’re most invested in just making sure that the experience feels really good and that things are actually working.”

Beyond the technical hurdles of the process, questions remain about how content will be moderated across the Fediverse. For example, Mastodon allows some artistic nudity, but Threads bars basically all cheeky photographs. So, what happens if someone posts a picture of their butt on Mastodon and you follow them through Threads? Would it appear in your feed despite Threads’ rules? Additionally, specifics are still murky regarding exactly how user data will be handled after the connections between networks are established. For example, if you federate a post from Threads and decide to delete it afterwards, what happens to the cached post on the servers of the other networks?

Another big, lingering question is why Meta wants to do this in the first place. Lambert says Meta wants to give users more control over their posts and followers, with easier avenues to engage across platforms. In the context of previous antitrust complaints from the US Federal Trade Commission, it’s also possible the company is trying to project an image to regulators that’s more open overall and welcoming to healthy competition.

If decentralization and interoperability become foundational to the next generation of online experiences, Meta is determined to prevail as at least one part of the sprawling conversation about autonomy and freedom of choice. “It really does feel like we’re kind of on the verge of this new era of social media,” Lambert says. “We have some ideas of what it might look like, but there’s still so much for us to learn.”

Updated: 2/2/2024, 1:14 pm EST: Added clarification about voice posts on Threads.

I’ll never use Threads or any other platform from that sociopathic transnational corporation Meta. This low quality article does nothing except confirm that’s the correct approach.