Fediverse on emsenn.net

Standardization as Counterinsurgency

Tue, 03 Mar 2026 00:00:00 +0000

This concept has a full treatment at technology/concepts/internet/topics/activitypub/concepts/standardization-as-counterinsurgency.

Federation

Wed, 31 Dec 2025 00:00:00 +0000

Federation is the network architecture in which autonomous servers exchange activities via a shared protocol — in this case, ActivityPub. Each server (instance) operates independently: it runs its own moderation policies, stores its own data, and decides which other instances to communicate with. Federation means these independent servers can interoperate, allowing users on one instance to follow, message, and interact with users on another.

The key property of federation is that no single server controls the network. An instance can join or leave the federation, block specific other instances, or modify how it processes incoming activities. This is what gave the early fediverse its character as an insurgent infrastructure: anyone could spin up a server and participate on equal technical footing.

Fediverse Overview

Wed, 31 Dec 2025 00:00:00 +0000

The fediverse is a network of federated services that exchange social activities.

Genealogy of the Fediverse

Wed, 31 Dec 2025 00:00:00 +0000

This genealogy traces how federated social networks emerged from decentralized communication protocols.

History of the Fediverse

Wed, 31 Dec 2025 00:00:00 +0000

This history summarizes the growth of federated social platforms and protocols.

ActivityPub: Institutional Capture of Insurgent Protocol

Fri, 05 Dec 2025 00:00:00 +0000

1. Introduction: From Insurgent Protocol to Institutional Dead Zone

In the last decade, the “fediverse” has been widely promoted as a concrete manifestation of a different kind of social web: one built on federation rather than platform enclosure, local governance rather than global terms of service, and open protocols rather than proprietary APIs. At the center of this story sits ActivityPub, a protocol standardized at the World Wide Web Consortium (W3C) and frequently described as the technical backbone of decentralized social networking. Mastodon, the most visible ActivityPub-based platform, has become the public face of this alternative. From the perspective of traditional web governance, ActivityPub looks like a success story. A grassroots set of practices and experiments coalesced into a protocol; the protocol was taken up by a major standards body; a flagship implementation gained substantial public recognition; large firms, including Meta, announced plans to integrate with it. The story appears to track the standard life-cycle of web technologies: experimental beginnings, formal consolidation, and eventual mainstream adoption. Yet the trajectory of Meta’s Threads—its attempt to plug a large-scale commercial social network into ActivityPub and “join the fediverse”—complicates this narrative. Despite intensive publicity, regulatory interest in interoperability, and the symbolic weight of a major platform endorsing a W3C standard, Threads’ federation has so far failed to either (a) transform the fediverse into a profitable growth engine for Meta or (b) establish ActivityPub as a living, generative substrate for a new kind of social web. Federated support exists, but it is marginal to Threads’ core product. Many fediverse communities remain skeptical or actively hostile. The promise of a vibrant, open ecosystem lubricated by a neutral standard has not materialized. This paper starts from that tension. Why does a protocol that appears to have successfully navigated the standards pipeline—and attracted the attention of one of the world’s largest platforms—produce such an anemic result, both politically and economically? Why does a success in the language of standards bodies (a W3C Recommendation, a large deployed base, corporate adoption) coincide with a sense that something has gone dead at the heart of the “open social web” project? We argue that these outcomes are symptomatic of a deeper structural dynamic: standardization as counterinsurgency. By this we mean a patterned institutional response in which standards bodies absorb infrastructural projects that originate as challenges to the dominant platform order, translate them into narrow technical artifacts, and stabilize them in forms that are highly legible to corporate and regulatory actors but stripped of much of their generative and political force. To develop this argument, we introduce three linked concepts: