FedBOX is a simple ActivityPub enabled server. Its goal is to serve as a reference implementation for the rest of the GoActivityPub packages.
It provides the base for some of the common functionality that such a service would require, such as: HTTP handlers and middlewares, storage and filtering etc.
The current iteration can persist data to BoltDB, Badger, SQLite and directly on the file system, but I want to also add support for PostgreSQL.
- Support for content management actitivies:
Create,Update,Delete. Follow,Accept,Rejectwith actors as objects.- Appreciation activities:
Like,Dislike. - Reaction activities:
Blockon actors,Flagon objects. - Negating content management and appreciation activities using
Undo. - OAuth2 authentication
- Support the same operations as the client to server activities.
- Capabilities of generating and loading HTTP Signatures from requests.
See the INSTALL file.
If you are interested in using FedBOX from an application developer point of view, make sure to read the Client to Server document, which details how the local flavour of ActivityPub C2S API can be used.
More information about FedBOX and the other packages in the GoActivityPub library can be found on the wiki.
If you have problems, questions, ideas or suggestions, please contact us by posting to the mailing list, or on GitHub. If you desire quick feedback, the mailing list is preferred, as the GitHub issues are not checked very often.