Website of https://litepub.social/

ap-compat.md (1298B)

  1. ---
  2. title: "LitePub for ActivityPub Implementors"
  3. ---
  4. ## JSON-LD context
  5. LitePub implementations are not required to use `@context` properties on their messages.
  6. A conformant ActivityPub implementation is required to process these messages with an
  7. injected `@context` of `"https://www.w3.org/ns/activitystreams"` as described in the
  8. [ActivityStreams 2.0 Core Specification][AS2-CORE-JSON-LD].
  9. [AS2-CORE-JSON-LD]: https://www.w3.org/TR/activitystreams-core/#jsonld
  10. However, the LitePub Core Vocabulary differs from the ActivityStreams 2.0 Vocabulary.
  11. It is suggested that LitePub implementations supply a locally hosted version of the
  12. [LitePub JSON-LD Context][litepub-jsonld] as their `@context`. It may be useful to
  13. inject a local copy of the LitePub JSON-LD Context instead of the default ActivityStreams
  14. 2.0 context when a message is received without a `@context` as it defines the full
  15. LitePub Core Vocabulary in a way that is useful to JSON-LD processors.
  16. [litepub-jsonld]: https://litepub.social/litepub/context.jsonld
  17. ## Signatures
  18. LitePub implementations MUST use HTTP Signatures to verify the authenticity of
  19. messages being delivered to or from peering nodes. The details surrounding
  20. the way HTTP Signatures are implemented in LitePub are discussed on the Overview
  21. page.