Meta plans on joining the fediverse - the responses

Meta is planning on joining the fediverse. There are early plans on making a decentralized network with ActivityPub, so that it connects to the fediverse. This lead to a lot of different reactions within the community. This article documents some of the different types of responses.

Meta plans on joining the fediverse - the responses

This week, news got out that Meta is making a plan to build a decentralized text-based social network. It would be a competitor to Twitter that uses ActivityPub, and would thus be part of the fediverse. The news broke on the website MoneyControl, who saw a copy of a product brief. A few hours later, the news got confirmed by Meta to the newsletter Platformer. Both articles have all the details and the best analysis, so if you want to get in-depth information check those out. The short summary is as follows:

  • The project is in the earliest stages, it is unclear if it is still in the ideas-phase or if development work has begun.
  • It is a "separate space where creators and public figures can share timely updates about their interests.”
  • Users can log in using their existing Instagram credentials.
  • The MVP of the project is to be able to send content. The idea seems to be that you can send text-based content out to people on other servers (such as Mastodon).
  • Being able to receive content or follow people from other servers is up in the air. A source says that it "may or may not enable" this.

This news has caused some serious waves in the fediverse. People have significantly different opinions and ideas about this news. In this article I document some of the main lines of thinking that I've encountered. At this point we have no idea how this will actually play out, especially since Meta is so early in the development of the project. But it is a milestone in the history of the fediverse, a validation that Big Tech wants to be a part of it all.

In order to understand this development, here are some of the main types of responses that have been played out on the feeds. The documentation is here is to help understand how different people have varying ideas about this all.

Validation of the fediverse

Mastodon's lead developer Eugen Rochko gave a positive statement on the development, stating:

This way of thinking, the validation of the value of decentralized social networks, was also echoed here by Chris Trottier, who further added that all Meta's recent successes are either acquired or copied, giving him confidence that it will not be easy for Meta to take over the fediverse. He also emphases the validation that this gives to the decentralized social networks, enabling and confirming other developers that want to work on the fediverse.

Extend Embrace Extinguish

A common response in the feeds is to call this an Extend Embrace Extinguish strategy by Meta. This seems to be one of the more common responses by people. Flipboard CEO Mike McCrue (who recently set up a Mastodon server for Flipboard as well), spells out in more detail how this strategy works:

Another thread points out the risk of the strategy by Meta by building an app that has features that people want, but are currently only partially available on the fediverse, such as search and quote posting. The same thread also points to the possibility of Meta forgoing hosting a server alltogether, and only providing access to the fediverse via a third-party client.

Historical parallels

As part of calling this the Embrace Extend Extinguish strategy by Meta, is some reflection by people on earlier open source standards. Some people reflected on how email became dominated by a few giants, and that it is surprisingly hard to run your own email server now. This draws direct parallels to fears that people have on the fediverse, where it only becomes possible to really join the fediverse via some large instances, and small instances do not get federated properly due to spam concerns. Other reflections on how Google did this with search, and the power that comes with the large size that big tech giants have. Similar arguments are also made about XMPP, and how adoption for this was destroyed, leading to the fragmentation of chat platforms.

A notable historical reference was made here, pointing out the history that Facebook and Friendica have. Friendica used to interoperate with Facebook, but Facebook shut that down years ago.

Working on standards

Another line of arguments is the need to further work on the ActivityPub standards that powers the fediverse. This thread goes into more detail about the risk that the fediverse faces with the immaturity of its standards and issues with the implementation of interoperability. The core argument is that big players can set rules in incompatible ways, because there is no strong protection against that. This does not need to happen on purpose, but can even happen by accident. Another thread that calls on the ActivityPub Working Group that created the standard with the W3C to spring into action again. The discussion involves one of the co-creators of the standard, where she points out some of the practical difficulties, especially regarding funding.

Looking forward

At this point in time, there are way to many unknowns to make a proper prediction of what is actually going to happen. But the variety of responses show that multiple ideas and reactions can be valid at the same time. Meta joining the fediverse is indeed a validation of the power of decentralized networks, while at the same time providing risks in specific ways. And even without Meta, there is value in standardizing the way different software interacts with the fediverse, helping it grow. At the same time, it can help prevent organisations to implement ActivityPub in ways that are incompatible, either on purpose or by accident.