Document AP and nodeinfo extensions #778
No reviewers
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#778
Loading…
Reference in a new issue
No description provided.
Delete branch "Oneric/akkoma:doc_ap-extensions"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 inpleroma/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...”). Thev1
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 indabd535e43
.Document AP and nodeinfo extensiosnto Document AP and nodeinfo extensions90d1fdb13e
to35b19aaa37
35b19aaa37
to60ec13eafa
60ec13eafa
to789bcfabec
789bcfabec
to076529b154
076529b154
to7272c7a95c
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
Thanks for explaining, fixed this and all other comments
@ -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
@ -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
7272c7a95c
to05eda169fe