OjakA bridge between your application and the fediverse.

A Rust framework for ActivityPub applications, named for Ojakgyo (오작교, 烏鵲橋), the bridge of crows and magpies across the Milky Way.

The application owns its data

Ojak never holds a follower, a post or an account of its own. It asks the application, and does the protocol around what it is told.

Both HTTP Signature schemes and FEP-8b32 proofs, held to one policy, and nothing embedded trusted that its sender cannot vouch for.

Documents are read by what their keys stand for, over contexts Ojak ships instead of fetches, and written back in one spelling.

Objects whose identity is a key rather than a hostname (FEP-ef61), signed with a key that need not live on the server.