Crate ojak 

Ojak: an ActivityPub application framework.

The application owns its data, and Ojak does the protocol around it; see docs/guide/concepts.md. It has the guarded HTTP client every outgoing request goes through (client), signatures and proofs (sig), delivery of activities through a queue the application provides (deliverer), fetching documents from other servers (fetch), the JSON-LD contexts a Linked Data Signature is checked over when ojak does not ship them (contexts), the key-value store Ojak keeps its caches in (kv), serving actors, objects, collections, WebFinger and NodeInfo and receiving activities (federation), portable objects (FEP-ef61) at gateways (portable), and finding an actor by its handle (webfinger).

Re-exports

pub use ojak_sig as sig;

Modules

client

The HTTP client every request Ojak sends goes through.

contexts

JSON-LD contexts ojak does not ship, fetched to check a Linked Data Signature as Mastodon checks one.

deliverer

Sending activities through the queue.

federation

Serving: what Ojak answers when another server, or a person, sends a GET.

fetch

Fetching documents from other servers.

kv

The key-value store Ojak keeps its caches in: a backend the application picks.

origin

Where an identifier’s authority comes from.

portable

Portable objects (FEP-ef61): verifying them, and signing them.

queue

The queue work waits in until it is done: a backend the application picks.

synchronization

Followers collection synchronization (FEP-8fcf): the digest of the followers a server holds for an actor, and the Collection-Synchronization header that carries it on a delivery, so that the receiving server can tell when its idea of who follows the actor there has drifted.

template

URI templates: the one description of a route that both matches requests and builds URIs.

webfinger

Finding an actor by its handle, through WebFinger (RFC 7033).