activitypub
—
notes about the azorius implementation
The azorius(1) server processes
activities using the ActivityPub
protocol to exchange
messages with other servers. The specification is subject to interpretation,
and not all implementations behave in the same way. This document attempts to
clarify azorius's behavior. It is not intended to be a complete description of
ActivityPub
, but may be useful as a guide to other
implementors looking to interoperate.
The following object or document types are supported.
- Page
- Used for posts. This is the object that azorius expects to receive for
posts and links.
- Note
- Used for comments. Will not in general work as replacement for Page.
- ChatMessage
- Used for chat.
Azorius primarily supports HTML content, not markdown or other
formats, with a wide range of permitted HTML tags in object
content fields.
The following activities are supported.
- Create
- Supported.
- Announce
- Groups will forward activities to followers using Announce.
- Follow
- Can follow both groups and persons.
- Update
- Supported.
- Delete
- Does what it can.
- Like
- Not yet implemented.
The following additional object types are supported, typically as
tag or attachment.
- Link
- The URL link for a Page.
- Image
- For attached images.
- Document
- As a variant of Image.
- Hashtag
- Limited.
Azorius uses http signatures.
Azorius implements the webfinger end point but it is not
required for federation.
The ActivityPub standard is subject to interpretation.