logo

litepub.social

Website of https://litepub.social/

ap-compat.md (1298B)

    

  1. ---

  2. title: "LitePub for ActivityPub Implementors"

  3. ---

  4. 

  5. ## JSON-LD context

  6. 

  7. LitePub implementations are not required to use `@context` properties on their messages.  

  8. A conformant ActivityPub implementation is required to process these messages with an

  9. injected `@context` of `"https://www.w3.org/ns/activitystreams"` as described in the

  10. [ActivityStreams 2.0 Core Specification][AS2-CORE-JSON-LD].

  11. 

  12.    [AS2-CORE-JSON-LD]: https://www.w3.org/TR/activitystreams-core/#jsonld

  13. 

  14. However, the LitePub Core Vocabulary differs from the ActivityStreams 2.0 Vocabulary.

  15. It is suggested that LitePub implementations supply a locally hosted version of the

  16. [LitePub JSON-LD Context][litepub-jsonld] as their `@context`.  It may be useful to

  17. inject a local copy of the LitePub JSON-LD Context instead of the default ActivityStreams

  18. 2.0 context when a message is received without a `@context` as it defines the full

  19. LitePub Core Vocabulary in a way that is useful to JSON-LD processors.

  20. 

  21.    [litepub-jsonld]: https://litepub.social/litepub/context.jsonld

  22. 

  23. 

  24. ## Signatures

  25. 

  26. LitePub implementations MUST use HTTP Signatures to verify the authenticity of

  27. messages being delivered to or from peering nodes.  The details surrounding

  28. the way HTTP Signatures are implemented in LitePub are discussed on the Overview

  29. page.