What Is the Role of an Actor Identifier in ActivityPub?

A name is not the same as an identifier

A person may recognize an account by its display name, but names can be duplicated or changed. Protocols need a reference that lets other systems identify which actor is meant. In ActivityPub, an actor identifier serves this role within the protocol’s linked data: other records can refer to the actor without relying on a display label. The identifier is a reference, not a promise that every client will present the same profile or that the account will remain available forever.

Connect profile data to actions

An actor’s published representation can provide information about the actor and links to relevant protocol endpoints. Activities then identify the actor responsible for an action. A receiving system can use that stable reference to connect the activity to the actor information it has retrieved or stored, and to interpret related protocol data.

For example, if an incoming activity names actor A as its creator, a receiver can compare that identifier with the actor identity associated with the sender and its stored profile data. This gives the receiver a consistent key for relationships such as attribution and following. A display name such as “River” is useful to a person, but it is not enough to disambiguate accounts across servers.

Treat identifiers as references that need checking

A consumer should use the protocol’s rules to resolve and validate an actor identifier, rather than assuming that a string that looks familiar proves who sent a request. Systems may need to check that the fetched actor data corresponds to the identifier and that the request is authorized under the protocol. Caching can help performance, but cached profile data can become stale; implementations need a considered refresh strategy appropriate to their behavior.

An identifier can also be referenced in stored activities after the actor changes profile details. Keeping the reference distinct from mutable presentation fields lets a client update a display name without rewriting the identity of every past activity.

Use stable identity carefully in interfaces

Interfaces can show a human-readable name alongside an account’s identifying information, helping users recognize both the person-facing label and the protocol reference. Avoid silently treating a name change as a new actor or assuming that two identical display names belong to one account. The actor identifier connects profile metadata and protocol actions, while receiver checks establish how much trust to place in a particular request. That distinction supports clearer records and safer federation.