Document AP and nodeinfo extensions #778

Merged
floatingghost merged 1 commit from Oneric/akkoma:doc_ap-extensions into develop 2024-05-27 01:34:58 +00:00
Member

And while add it point to this via a top-level FEDERATION.md document as standardised by FEP-67ff.

I documented all extensions i could think of but it’s possible i missed some.

list scope and listMessage are actually semi-broken atm and afaik basically unused anyway and might be better to remove in a future PR (see #akkoma-dev).

suggestions is hardcoded to false in pleroma/web/nodeinfo/nodeinfo.ex, but changing it to true there still has an effect on akkoma-fe; it will display a “Who to follow” sidebar on the left *(but be stuck in “Loading...”). The v1 version of the suggestions API used to be implemented via third-party recommendations services and more keys with details about the configured service sued to be present, but this got removed in dabd535e43.

And while add it point to this via a top-level `FEDERATION.md` document as standardised by FEP-67ff. I documented all extensions i could think of but it’s possible i missed some. list scope and listMessage are actually semi-broken atm and afaik basically unused anyway and might be better to remove in a future PR *(see `#akkoma-dev`)*. `suggestions` is hardcoded to false in `pleroma/web/nodeinfo/nodeinfo.ex`, but changing it to true there still has an effect on akkoma-fe; it will display a “Who to follow” sidebar on the left *(but be stuck in “Loading...”). The `v1` version of the suggestions API used to be implemented via third-party recommendations services and more keys with details about the configured service sued to be present, but this got removed in dabd535e436789e64f6630460bfadd2f49dcf069.
Oneric added 1 commit 2024-05-17 00:27:24 +00:00
Document AP and nodeinfo extensiosn
Some checks are pending
ci/woodpecker/pr/build-amd64 Pipeline is pending
ci/woodpecker/pr/build-arm64 Pipeline is pending
ci/woodpecker/pr/docs Pipeline is pending
ci/woodpecker/pr/lint Pipeline is pending
ci/woodpecker/pr/test Pipeline is pending
90d1fdb13e
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.
Oneric changed title from Document AP and nodeinfo extensiosn to Document AP and nodeinfo extensions 2024-05-17 00:27:34 +00:00
Oneric force-pushed doc_ap-extensions from 90d1fdb13e to 35b19aaa37 2024-05-17 00:27:58 +00:00 Compare
Oneric force-pushed doc_ap-extensions from 35b19aaa37 to 60ec13eafa 2024-05-17 00:30:28 +00:00 Compare
Oneric force-pushed doc_ap-extensions from 60ec13eafa to 789bcfabec 2024-05-17 02:42:13 +00:00 Compare
Oneric force-pushed doc_ap-extensions from 789bcfabec to 076529b154 2024-05-17 02:57:17 +00:00 Compare
Oneric force-pushed doc_ap-extensions from 076529b154 to 7272c7a95c 2024-05-25 00:59:48 +00:00 Compare
floatingghost reviewed 2024-05-26 16:37:14 +00:00
floatingghost left a comment
Owner

a few little grammar thingies but the docs look very nice

a few little grammar thingies but the docs look very nice
@ -15,0 +84,4 @@
```
!!! note
Albeit an emoji reaction can only contain a single emoji,

Albeit -> although

albeit is used exclusively as a conjunction and can't be used in this sort of context

Albeit -> although albeit is used exclusively as a conjunction and can't be used in this sort of context
Author
Member

Thanks for explaining, fixed this and all other comments

Thanks for explaining, fixed this and all other comments
Oneric marked this conversation as resolved
@ -15,0 +235,4 @@
Currently Akkoma, just like Mastodon, only properly supports a single language entry,
in case of multiple entries a random language will be picked.
Furthermore, atm Akkoma will always read the `content` field and

i mean i understand it, but the acronym probably shouldn't be here

i mean _i_ understand it, but the acronym probably shouldn't be here
Oneric marked this conversation as resolved
@ -15,0 +256,4 @@
An implementation creating a new post MUST NOT address both the local and
general public scope `as:Public` at the same time. A post addressing the local
scope MUST NOT be sent to other instances or be possible to fetch by other
instances regardless of potential other listed addressants..

addressants -> addressees

addressants -> addressees
Oneric marked this conversation as resolved
Oneric force-pushed doc_ap-extensions from 7272c7a95c to 05eda169fe 2024-05-26 17:08:14 +00:00 Compare
floatingghost merged commit cdc918c8f1 into develop 2024-05-27 01:34:58 +00:00
floatingghost deleted branch doc_ap-extensions 2024-05-27 01:34:59 +00:00
Sign in to join this conversation.
No description provided.