ActivityPub
This service allows you to create an ActivityPub server with data stored in a triple store.
#
Features- Store activities, actors and objects in the triple store
- Handle all kind of ontologies (see
additionalContext
setting) - Allow to create actors when new WebIDs are created
- Currently supported activities:
Create
Update
Delete
Follow
#
Dependencies#
Sub-services- ActivityService
- ActorService
- CollectionService
- FollowService
- InboxService
- ObjectService
- OutboxService
#
Install#
Usage#
Configure the LDP containersThe containers for actors and objects are handled through the LDP service. You need to define containers with ActivityStreams's actors and objects in the acceptedTypes
. Alternatively, you can load the default containers from the @semapps/activitypub
package as below:
#
Queue federation POSTsIf you want to make sure no data is lost when trying to POST to remote ActivityPub servers, you can set the queueServiceUrl
settings.
The Bull task manager will queue the task and you will be able to retry it if it fails.
#
Create actors on WebID creationsThis is done automatically when a webid.created
event is detected.
#
SettingsProperty | Type | Default | Description |
---|---|---|---|
baseUri | String | required | Base URI of your web server |
additionalContext | Object | The ActivityStreams ontology is the base ontology, but you can add more contexts here if you wish. | |
queueServiceUrl | String | Redis connection string. If set, the Bull task manager will be used to handle federation POSTs. |