akkoma/FEDERATION.md
ilja space dce07f05d9
Some checks are pending
ci/woodpecker/pr/build-amd64 Pipeline is pending approval
ci/woodpecker/pr/build-arm64 Pipeline is pending approval
ci/woodpecker/pr/docs Pipeline is pending approval
ci/woodpecker/pr/lint Pipeline is pending approval
ci/woodpecker/pr/test Pipeline is pending approval
ci/woodpecker/pull_request_closed/lint Pipeline was successful
ci/woodpecker/pull_request_closed/test Pipeline was successful
ci/woodpecker/pull_request_closed/build-amd64 Pipeline was successful
ci/woodpecker/pull_request_closed/build-arm64 Pipeline was successful
ci/woodpecker/pull_request_closed/docs Pipeline was successful
Merge branch 'develop' of https://akkoma.dev/AkkomaGang/akkoma into use_fep-c16b_formatting_mfm_functions
2025-02-23 10:13:44 +01:00

1.9 KiB
Raw Permalink Blame History

Federation

Supported federation protocols and standards

Supported FEPs

ActivityPub

Akkoma mostly follows the server-to-server parts of the ActivityPub standard, but implements quirks for Mastodon compatibility as well as Mastodon-specific and custom extensions.

See our documentation and Mastodons federation information linked further below for details on these quirks and extensions.

Akkoma does not perform JSON-LD processing.

Required extensions

HTTP Signatures

All AP S2S POST requests to Akkoma instances MUST be signed. Depending on instance configuration the same may be true for GET requests.

FEP-c16b: Formatting MFM functions

The optional extension term htmlMfm is currently not used.

Nodeinfo

Akkoma provides many additional entries in its nodeinfo response, see the documentation linked below for details.

Additional documentation