A better Rust ATProto crate
Rust 99.8%
Nix 0.1%
Shell 0.1%
Just 0.1%
Python 0.1%
Other 0.1%
401 5 0

Clone this repository

https://tangled.org/nonbinary.computer/jacquard https://tangled.org/did:plc:yfvwmnlztr4dwkb7hwz55r2g/jacquard
[email protected]:nonbinary.computer/jacquard [email protected]:did:plc:yfvwmnlztr4dwkb7hwz55r2g/jacquard

For self-hosted knots, clone URLs may differ based on your setup.

Download tar.gz
README.md

Crates.io Documentation ko-fi

Jacquard#

A suite of Rust crates intended to make it much easier to get started with atproto development, without sacrificing flexibility or performance.

Jacquard is simpler because it is designed in a way which makes things simple that almost every other atproto library seems to make difficult.

It is also designed around zero-copy/borrowed deserialization: types like Post<'_> can borrow data (via the CowStr<'_> type and a host of other types built on top of it) directly from the response buffer instead of allocating owned copies. Owned versions are themselves mostly inlined or reference-counted pointers and are therefore still quite efficient. The IntoStatic trait (which is derivable) makes it easy to get an owned version and avoid worrying about lifetimes.

Features#

  • Validated, spec-compliant, easy to work with, and performant baseline types
  • Designed such that you can just work with generated API bindings easily
  • Straightforward OAuth
  • Server-side convenience features
  • Lexicon Data value type for working with unknown atproto data (dag-cbor or json)
  • An order of magnitude less boilerplate than some existing crates
  • Batteries-included, but easily replaceable batteries.
    • Easy to extend with custom lexicons using code generation or handwritten api types
    • Stateless options (or options where you handle the state) for rolling your own
    • All the building blocks of the convenient abstractions are available
    • Use as much or as little from the crates as you need

Example#

Dead simple API client. Logs in with OAuth and prints the latest 5 posts from your timeline.

// Note: this requires the `loopback` feature enabled (it is currently by default)
use clap::Parser;
use jacquard::CowStr;
use jacquard::api::app_bsky::feed::get_timeline::GetTimeline;
use jacquard::client::{Agent, FileAuthStore};
use jacquard::oauth::client::OAuthClient;
use jacquard::oauth::loopback::LoopbackConfig;
use jacquard::types::xrpc::XrpcClient;
use miette::IntoDiagnostic;

#[derive(Parser, Debug)]
#[command(author, version, about = "Jacquard - OAuth (DPoP) loopback demo")]
struct Args {
    /// Handle (e.g., alice.bsky.social), DID, or PDS URL
    input: CowStr<'static>,

    /// Path to auth store file (will be created if missing)
    #[arg(long, default_value = "/tmp/jacquard-oauth-session.json")]
    store: String,
}

#[tokio::main]
async fn main() -> miette::Result<()> {
    let args = Args::parse();

    // Build an OAuth client with file-backed auth store and default localhost config
    let oauth = OAuthClient::with_default_config(FileAuthStore::new(&args.store));
    // Authenticate with a PDS, using a loopback server to handle the callback flow
    let session = oauth
        .login_with_local_server(
            args.input.clone(),
            Default::default(),
            LoopbackConfig::default(),
        )
        .await?;
    // Wrap in Agent and fetch the timeline
    let agent: Agent<_> = Agent::from(session);
    let timeline = agent
        .send(&GetTimeline::new().limit(5).build())
        .await?
        .into_output()?;
    for (i, post) in timeline.feed.iter().enumerate() {
        println!("\n{}. by {}", i + 1, post.post.author.handle);
        println!(
            "   {}",
            serde_json::to_string_pretty(&post.post.record).into_diagnostic()?
        );
    }

    Ok(())
}

If you have just installed, you can run the examples using just example {example-name} {ARGS} or just examples to see what's available.

WARNING

The latest version swaps from the url crate to the lighter and quicker fluent-uri. It also moves the re-exported crate paths around and renames the Uri<'_> value type enum to UriValue<'_> to avoid confusion. This is likely to have broken some things. Migrating is pretty straightforward but consider yourself forewarned. This crate is not 1.0 for a reason.

Changelog#

CHANGELOG.md

0.11 Release Highlights:#

  • jacquard-lexgen and jacquard-identity no longer depend on the generated API crate. This is mostly for my own benefit.

Code generation pipeline overhaul (jacquard-lexicon, jacquard-lexgen)

  • Jacquard's codegen output already was nice to use. now it's going to be nice to read.
  • New code generation tracks the types used, makes an import block for the file, and then organizes the file with stuff you care about at the top and internal stuff, like the builders, at the bottom.
  • Import resolution pass now conditionally generates short paths when types are unambiguous within a module, falling back to fully-qualified paths when collisions exist

0.10 Release Highlights:#

URL type migration

  • Migrated from url crate to fluent_uri for validated URL/URI types
  • All Url types are now Uri from fluent_uri
  • Affects any code that constructs, passes, or pattern-matches on endpoint URLs

Re-exported crate paths

  • Re-exported crates (including non-proc-macro dependencies of the generated API crate) are now centralized into a distinct module
  • Import paths for re-exported types have changed

no_std groundwork

  • Initial work toward allowing jacquard to function on platforms without access to the standard library.
  • std usage is now feature-gated. the library currently does not compile without std due to some remaining dependencies.

Projects using Jacquard#

Component crates#

Jacquard is broken up into several crates for modularity. The correct one to use is generally jacquard itself, as it re-exports most of the others.

jacquard Main crate Crates.io Documentation
jacquard-common Foundation crate Crates.io Documentation
jacquard-axum Axum extractor and other helpers Crates.io Documentation
jacquard-api Autogenerated API bindings Crates.io Documentation
jacquard-oauth atproto OAuth implementation Crates.io Documentation
jacquard-identity Identity resolution Crates.io Documentation
jacquard-repo Repository primitives (MST, commits, CAR I/O) Crates.io Documentation
jacquard-lexicon Lexicon parsing and code generation Crates.io Documentation
jacquard-lexgen Code generation binaries Crates.io Documentation
jacquard-derive Macros for lexicon types Crates.io Documentation

Testimonials#

Development#

This repo uses Flakes

# Dev shell
nix develop

# or run via cargo
nix develop -c cargo run

# build
nix build

There's also a justfile for Makefile-esque commands to be run inside of the devShell, and you can generally cargo ... or just ... whatever just fine if you don't want to use Nix and have the prerequisites installed.

License