AkkomaGang/akkoma
AkkomaGang/akkoma
14
64
Fork 85
Code Issues 165 Pull requests 16 Packages Projects 2 Releases 14 Wiki Activity
akkoma/FEDERATION.md
Oneric 05eda169fe
Some checks are pending
ci/woodpecker/pr/build-amd64 Pipeline is pending
Details
ci/woodpecker/pr/build-arm64 Pipeline is pending
Details
ci/woodpecker/pr/docs Pipeline is pending
Details
ci/woodpecker/pr/lint Pipeline is pending
Details
ci/woodpecker/pr/test Pipeline is pending
Details
Document AP and nodeinfo extensions 
And while add it point to this via a top-level
FEDERATION.md document as standardised by FEP-67ff.

Also add a few missing descriptions to the config cheatsheet
and move the recently removed C2S extension into an appropiate
subsection.
2024-05-26 19:04:06 +02:00

1.6 KiB
Raw 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 Mastodon’s 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.

Nodeinfo

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

Additional documentation