Commit f9f06d27 authored by Eugen Rochko's avatar Eugen Rochko

Update content/en/development/activitypub.md

parent 7fcb8746
Pipeline #502 passed with stages
in 17 seconds
......@@ -9,14 +9,14 @@ menu:
## APIs
- Mastodon supports the server-to-server part of the ActivityPub spec.
- It implements the HTTP signatures spec for authentication of inbox deliveries.
- Mastodon also supports Linked Data Signatures for forwarded payloads.
- Mastodon supports the server-to-server part of the [ActivityPub spec](https://www.w3.org/TR/activitypub/).
- It implements the [HTTP signatures spec](https://tools.ietf.org/html/draft-cavage-http-signatures-10) for authentication of inbox deliveries.
- Mastodon also supports [Linked Data Signatures](https://w3c-dvcg.github.io/ld-signatures/) for forwarded payloads.
## Restrictions
- Mastodon requires all object IDs to use the HTTPS schema.
- Mastodon also requires servers to offer a WebFinger endpoint for converting username/domain pairs into actors.
- Mastodon also requires servers to offer a [WebFinger](https://tools.ietf.org/html/rfc7033) endpoint for converting username/domain pairs into actors.
- Mastodon accepts `Application`, `Group`, `Organization`, `Person`, and `Service` as valid types for actors.
- Mastodon requires activities attributed to an actor to have an ID on the same host as the actor.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment