fep

FEP-336f: Creator Collaborations

Summary

This proposal describes how an object can credit one or more coauthors besides its author, with each coauthor’s consent, in a way that other servers can verify.

The author remains the only actor and attributedTo of the object, so software that does not implement this proposal sees an ordinary post. The object gains a coauthors property that references one CoauthorAuthorization per coauthor. Each authorization is published by the coauthor’s server, attributed to the coauthor, and states that the coauthor agreed to be credited on that specific object. Receivers dereference every authorization before showing a credit, and coauthors can withdraw their credit at any time.

This version covers coauthors who have an account on the same server as the author. Coauthorship across servers needs an invitation protocol, which is left for future work.

Motivation

Short-form video, photo and blogging platforms commonly let creators publish one post together, for example a collaboration between two musicians or a brand and a creator. The post appears on both creators’ profiles and reaches both audiences.

On the fediverse, the obvious encoding is a list of actors in attributedTo. That does not work well in practice:

This proposal keeps authority with a single author, makes the credit a separate, consent-backed statement by the coauthor, and lets receivers verify that statement against the coauthor’s own server.

History

Requirements

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this specification are to be interpreted as described in RFC 2119 and RFC 8174 when, and only when, they appear in all capitals, as shown here.

Terminology

Overview

  1. The author asks a coauthor on the same server to collaborate on an object.
  2. The coauthor agrees, either for that object or ahead of time for all objects by that author.
  3. The publishing server creates a CoauthorAuthorization, attributed to the coauthor, naming the object and the author.
  4. The object is published with a coauthors property that references the authorization, and is delivered to the author’s and the coauthor’s audiences.
  5. Receiving servers fetch each authorization by its id and check it before showing the credit.
  6. If the credit ends, the authorization is removed, the author sends an Update without it, and the coauthor sends a Delete of the authorization.

Coauthored objects

The coauthors property

A coauthored object has a coauthors property whose value is an array. Each element references one CoauthorAuthorization, either as an object with at least an id or as a bare id string. Publishing servers SHOULD use objects containing type, id and attributedTo:

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    "https://w3id.org/fep/336f"
  ],
  "id": "https://loops.example/ap/users/100/video/200",
  "type": "Note",
  "attributedTo": "https://loops.example/ap/users/100",
  "content": "<p>New track with @bob</p>",
  "published": "2026-10-27T10:00:00Z",
  "to": ["https://www.w3.org/ns/activitystreams#Public"],
  "cc": [
    "https://loops.example/ap/users/100/followers",
    "https://loops.example/ap/users/101",
    "https://loops.example/ap/users/101/followers"
  ],
  "attachment": [
    {
      "type": "Document",
      "mediaType": "video/mp4",
      "url": "https://cdn.loops.example/videos/200.mp4"
    }
  ],
  "coauthors": [
    {
      "type": "CoauthorAuthorization",
      "id": "https://loops.example/ap/users/101/coauthor_authorizations/300",
      "attributedTo": "https://loops.example/ap/users/101"
    }
  ]
}

The embedded attributedTo is a hint for display before verification. Receiving servers MUST NOT rely on it (see Verification).

A publishing server:

Addressing and delivery

When the object is visible beyond its mentioned recipients, the publishing server SHOULD:

Delivering to the coauthor’s followers is possible because the coauthor is on the publishing server. Update and Delete activities for the object SHOULD reach the same audience.

The coauthor’s actor is addressed without a Mention tag unless the content mentions them. Some implementations treat an addressed actor without a Mention as a silent mention.

CoauthorAuthorization

A CoauthorAuthorization is a public statement, made in the name of the coauthor, that they agreed to be credited on one object by one author.

Property Required Description
id MUST URL of the authorization. MUST be on the same origin as the coauthor’s actor.
type MUST CoauthorAuthorization
attributedTo MUST The coauthor’s actor.
interactingObject MUST The id of the coauthored object.
interactionTarget MUST The author’s actor, i.e. the object’s attributedTo.
published SHOULD When the coauthor gave consent.
{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    "https://w3id.org/fep/336f"
  ],
  "type": "CoauthorAuthorization",
  "id": "https://loops.example/ap/users/101/coauthor_authorizations/300",
  "attributedTo": "https://loops.example/ap/users/101",
  "interactingObject": "https://loops.example/ap/users/100/video/200",
  "interactionTarget": "https://loops.example/ap/users/100",
  "published": "2026-10-27T10:00:00Z"
}

Serving the authorization

The publishing server:

A publishing server MUST obtain the coauthor’s consent before listing them in coauthors. This proposal does not define how consent is collected on the server, but it MUST be an explicit action by the coauthor. Two forms are RECOMMENDED:

A publishing server SHOULD let users limit who can invite them (for example nobody, accounts they follow, mutuals, or everyone), and MUST NOT allow invitations between accounts where either one blocks the other.

While consent is pending, a publishing server MUST NOT list the coauthor. It MAY hold the whole object back until the coauthor answers. Loops holds the post, and if the invitation is declined or expires, lets the author publish it without the coauthor or discard it.

Verification

A receiving server MUST NOT show a coauthor credit based on the object alone. For each entry in coauthors, it MUST dereference the authorization from its id and accept the credit only if all of the following hold:

  1. The fetched document’s type is CoauthorAuthorization.
  2. The fetched document’s id equals the URL that was fetched.
  3. interactingObject equals the coauthored object’s id.
  4. interactionTarget equals the coauthored object’s attributedTo.
  5. attributedTo is an actor on the same origin as the authorization’s id, and resolves to an actor whose id equals that value.
  6. That actor is not the author.
  7. In this version of the proposal, the authorization’s origin is the same as the coauthored object’s origin.

Requirement 5 is what makes the authorization meaningful: under FEP-fe34, a document fetched from the coauthor’s origin speaks for the coauthor. Requirement 7 reflects that this version only covers coauthors on the author’s server. A future cross-server extension would relax it.

Entries that fail verification, cannot be fetched, or are not on an https URL MUST be ignored. The object itself MUST still be accepted and shown without the failed credits.

Receiving servers:

Updates

On Create, a missing or empty coauthors means the object has no coauthors.

On Update of a coauthored object:

Publishing servers SHOULD include coauthors in every Update of an object that currently has, or previously had, coauthors.

Withdrawal

A credit can end because the coauthor leaves, the author removes the coauthor, either account blocks the other, or the coauthor’s account is deleted. When this happens, the publishing server:

  1. MUST stop serving the authorization (see Serving the authorization).
  2. MUST send an Update of the object with the remaining coauthors, using an empty array if none remain.
  3. SHOULD send a Delete of the authorization from the coauthor’s actor to the object’s audience:
{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    "https://w3id.org/fep/336f"
  ],
  "id": "https://loops.example/ap/users/101/coauthor_authorizations/300#delete",
  "type": "Delete",
  "actor": "https://loops.example/ap/users/101",
  "to": ["https://www.w3.org/ns/activitystreams#Public"],
  "cc": ["https://loops.example/ap/users/100"],
  "object": {
    "id": "https://loops.example/ap/users/101/coauthor_authorizations/300",
    "type": "CoauthorAuthorization",
    "interactingObject": "https://loops.example/ap/users/100/video/200",
    "interactionTarget": "https://loops.example/ap/users/100"
  }
}

The Delete lets receivers drop the credit even if the Update is lost, and ties the withdrawal to the coauthor’s own signature. When account deletion triggers the withdrawal, publishing servers SHOULD send it before deleting the coauthor’s actor, so that receivers can still verify the signature.

A receiving server that gets a Delete whose object has type CoauthorAuthorization:

Receivers that re-fetch an authorization and get 404 or 410 MUST also remove the credit.

Compatibility

Security considerations

Privacy considerations

Future work

Implementations

JSON-LD context

The context document is published at https://w3id.org/fep/336f:

{
  "@context": {
    "fep336f": "https://w3id.org/fep/336f#",
    "gts": "https://gotosocial.org/ns#",
    "CoauthorAuthorization": "fep336f:CoauthorAuthorization",
    "coauthors": {
      "@id": "fep336f:coauthors",
      "@container": "@set"
    },
    "interactingObject": {
      "@id": "gts:interactingObject",
      "@type": "@id"
    },
    "interactionTarget": {
      "@id": "gts:interactionTarget",
      "@type": "@id"
    }
  }
}

Publishers MAY instead embed these term definitions directly in the object’s @context.

References

CC0 1.0 Universal (CC0 1.0) Public Domain Dedication

To the extent possible under law, the authors of this Fediverse Enhancement Proposal have waived all copyright and related or neighboring rights to this work.