Fediverse Enhancement Proposals
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
David Sterry 4a4e5059d0 Merge pull request 'FEP-e232: Add discussionsTo field, add @context to example' (#38) from silverpill/fep:e232-update into main 13 hours ago
ISSUE_TEMPLATE ISSUE_TEMPLATE/tracking_issue.md: Add template for tracking issue 2 years ago
feps FEP-e232: Add discussionsTo field, add @context to example 13 hours ago
EDITORS.md EDITORS: add Arnold Schrijver 1 year ago
LICENSE init 2 years ago
README.md Add FEP-2100 to the Overview table 19 hours ago
SUBMISSION.md SUBMISSION: Move to codeberg.org. 1 year ago
fep-0000-template.md FEP-a4ed: Draft updates 2 years ago


Fediverse Enhancement Proposals

This is the Git repository containing Fediverse Enhancment Proposals (FEPs).

A Fediverse Enhancement Proposal (FEP) is a document that provides information to the Fediverse community. The goal of a FEP is to improve interoperability and well-being of diverse services, applications and communities that form the Fediverse.


Title Status Tracking issue dateReceived dateFinalized (or dateWithdrawn)
FEP-a4ed: The Fediverse Enhancement Proposal Process FINAL #10 2020-10-16 2020-01-18
FEP-8fcf: Followers collection synchronization across servers FINAL #6 #11 2020-10-24 2022-02-07
FEP-f1d5: NodeInfo in Fediverse Software DRAFT #12 2020-12-13 -
FEP-400e: Publicly-appendable ActivityPub collections FINAL #5 2021-02-16 2020-02-04
FEP-8c3f: Web Monetization DRAFT #3 2022-01-18 -
FEP-2100: Unbound Group and Organization DRAFT #36 2022-03-31 -
FEP-e232: Object Links DRAFT #14 2022-08-01 -
FEP-5624: Per-object reply control policies DRAFT #18 2022-08-23 -
FEP-1b12: Group federation DRAFT #22 2022-11-12 -
FEP-8b32: Object Integrity Proofs DRAFT #29 2022-11-12 -
FEP-c390: Identity Proofs DRAFT #34 2022-11-23 -

Submitting a FEP

Do you have an idea, opinion or information that you want to share with the wider Fediverse community? You may do so with a Fediverse Enhancement Proposal (FEP).

To create and submit a FEP:

  1. Think of a title for the FEP you want to submit.
  2. Compute the identifier of the FEP by computing the hash of the title. This can be done with following Unix command:
$ echo -n "The title of my proposal" | sha256sum | cut -c-4
  1. Clone this repository.
  2. Copy the FEP template (fep-0000-template.md) to the feps/ folder and change the filename to fep-abcd.md where abcd is the identifier computed in step 2.
  3. Write down your idea in the newly created file.
  4. Submit a Pull Request to this repository containing your proposal (other submission methods may be listed in SUBMISSION.md).
  5. Within 7 days you will receive feedback from the editors who may request changes or clarifications. If your proposal is accepted it will be added to the repository with the status DRAFT. The editors will also create a tracking issue for your proposal.
  6. You (as author) are now responsible for initiating community discussion and collecting feedback (post links to the discussions to the tracking issue). While the proposal is in status DRAFT you may submit changes to the proposal via Pull Requests (reference the tracking issue from the Pull Request).
  7. After at least 60 days of being added to the repository with status DRAFT you may request the proposal to be finalized. You must now request final comments from the community. If there are no significant community objections your proposal will reach status FINAL after 14 days. Once the proposal has reached status FINAL it may no longer be updated.

For more information see FEP-a4ed: The Fediverse Enhancement Proposal Process.


Editors are listed in the EDITORS.md file.


CC0 1.0 Universal (CC0 1.0) Public Domain Dedication

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