Open web

ActivityPub explained

ActivityPub is a W3C Recommendation for social networking. It gives compatible software a common way to represent people and services, describe actions and deliver those actions between systems.

Actors and activities

An actor can represent a person, group, service or application. Activities describe things actors do: creating an object, following another actor, announcing something or indicating a preference. The data is structured so different software can interpret the same basic meaning while presenting it in its own interface.

Inboxes and outboxes

The standard describes an outbox where an actor’s activities can be made available and inboxes that receive relevant activities. In server-to-server federation, software discovers remote actors and sends signed requests to the appropriate inboxes. A Mastodon user does not need to manage this plumbing; the home server does it.

The normative details are in the W3C ActivityPub Recommendation. ActivityPub builds on the vocabulary and data model described by ActivityStreams 2.0.

A standard does not make every service identical

Implementations can support different features and object types. One service may emphasise short posts, another photos or long articles. Common activities can travel between them, while specialised features may be simplified, ignored or displayed differently. Compatibility is a spectrum shaped by both standards and implementation choices.

Moderation remains local

ActivityPub enables communication; it does not impose one global rulebook. Servers authenticate requests, choose what to accept, filter or reject, and apply their own policies. Open protocols make independent services possible, but operators still need security, abuse handling, reliable infrastructure and responsible data practices.

Why it matters

Protocol-based social networking allows communities to change software or governance without requiring one company to own every identity and conversation. It also introduces complexity: delivery paths cross administrative boundaries, features differ and trust must be evaluated locally. Understanding that balance is the best way to approach the fediverse without either hype or unnecessary fear.

Return to fediverse basics →