AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
A bridge between your application and the fediverse.
Developer toolsRustGitHub @eunha-spaceOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Rust library for implementing ActivityPub applications.
Translation pending
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
Ojak ==== A bridge between your application and the fediverse. Ojak is a Rust framework for building ActivityPub applications. Your application keeps its own data: it says where its actors, objects and collections live, supplies them from its own storage, and decides what to do with what arrives. Ojak does the protocol around them: serving, verifying, fetching and delivering. The name comes from Ojakgyo (오작교, 烏鵲橋), the bridge of crows and magpies that, in the Korean telling of the Weaver and the Herdsman, spans the Milky Way so that two stars kept apart can meet.Read the full README ↗
A bridge between your application and the fediverse.
Ojak is a Rust framework for building ActivityPub applications. Your application keeps its own data: it says where its actors, objects and collections live, supplies them from its own storage, and decides what to do with what arrives. Ojak does the protocol around them: serving, verifying, fetching and delivering.
The name comes from Ojakgyo (오작교, 烏鵲橋), the bridge of crows and magpies that, in the Korean telling of the Weaver and the Herdsman, spans the Milky Way so that two stars kept apart can meet.
Documentation, including a getting started guide, is at https://ojak.dev/.
Ojak is young, and its APIs may still change. It is not on crates.io yet, so depend on it through Git:
[dependencies]
ojak = { git = "https://github.com/eunha-space/ojak.git" }
What does no I/O is kept apart from what does. The vocabulary and JSON-LD
crates are no_std, and signatures and proofs are a crate of their own that
takes bytes, keys and the time rather than fetching or reading them. The
crate list says what is where.
Ojak is licensed under the GNU Affero General Public License v3.0. See LICENSE for details.