This implementation aims to be a fully compliant ActivityPub server using JWTs with SHDW Drive and IPFS support.
https://www.w3.org/TR/activitypub/
Current Status: Pre-Alpha (WIP)
- FastAPI
- MongoDB
- MONGO_URL
- REDIS_URL
- SERVER_PRIVATE_KEY
- BASE_URL
- HS256_SECRET_KEY
- RS256_PRIVATE_KEY
- RS256_PUBLIC_KEY
- JWT_ALGORITHM (optional - defaults to HS256)
- Shared server- & client-to-server
- Inbox GET
- Outbox GET
- Shared inbox GET
- Resource GET
- Object
- Actor
- Activity
- Collections
- Special collections
- Inbox
- Outbox
- Followers
- Following
- Liked
- Shares
- Misc collections (of activities)
- Pagination
- Special collections
- Relay requests for remote objects
- Response code 410 for Tombstones
- Security
- Permission-based filtering
- Server-to-server
- Inbox POST
- Activity side-effects
- Create
- Update
- Delete
- Follow
- Accept
- Reject
- Add
- Remove
- Like
- Announce
- Undo
- Block
- Security
- Signature validation
- Honor recipient blocklist
- Recursive resolution of related objects
- Forwarding from inbox
- Activity side-effects
- Shared inbox POST
- Delivery to targeted local inboxes
- Delivery
- Request signing
- Addressing
- Shared inbox optmization
- Direct delivery to local inboxes
- Redelivery attempts
- Inbox POST
- Client-to-server
- Outbox POST
- Auto-Create for bare objects
- Activity side-effects
- Create
- Update
- Delete
- Follow
- Accept
- Reject
- Add
- Remove
- Like
- Announce
- Undo
- Block
- Media upload
- Outbox POST
- Other
- Actor creation
- Key generation
- Security
- Verification
- localhost block
- Recursive object resolution depth limit
- Related standards
- http-signature
- webfinger
- json-ld
- Context cache
- nodeinfo
- Linked data signatures
- Storage model (denormalized MongoDB)
- Index coverage for all queries
- Fully interchangeable with documented API
- Actor creation