Standards support
ActivityPods is built on open standards from the Solid and ActivityPub ecosystems. The table below summarizes what is supported by Pod providers. See the other pages of this section for more details.
| Standard | Support | Notes |
|---|---|---|
| ActivityPub | ✅ Yes | Client-to-server and server-to-server. The proxy endpoint is extended to all HTTP methods. |
| Webfinger | ✅ Yes | See Identity. |
| HTTP Signatures | ✅ Yes | Cavage draft, as used in the Fediverse. Accepted on all endpoints, not only inboxes. |
| Linked Data Signatures | ❌ No | |
| Nodeinfo | ✅ Yes | Version 2.1. |
| Linked Data Platform | 🟡 Partial | Basic containers only. Binaries are supported. See Resources management. |
| LDP Paging | ✅ Yes | With additional sorting and filtering. See Containers paging. |
| Solid Protocol | 🟡 Partial | No N3 Patch (SPARQL Update is supported), no WAC-Allow header. |
| Solid-OIDC | 🟡 Partial | No DPoP. See Authentication. |
| Web Access Control | ✅ Yes | Except the WAC-Allow header. |
| Access Control Policy | ❌ No | |
| Solid Application Interoperability | 🟡 Partial | Without Data Authorizations and Data Grants. See Application interoperability. |
| Type Indexes | ✅ Yes | Public and private. Uses a custom predicate to link the registrations. |
| Solid Notifications | ✅ Yes | WebSocketChannel2023 and WebhookChannel2023. See Live update. |
| Verifiable Credentials | ✅ Yes | VC API v0.3, eddsa-rdfc-2022 cryptosuite. See Authorization. |
| WebID-TLS | ❌ No | Not planned. |