[![Crates.io](https://img.shields.io/crates/v/jacquard.svg)](https://crates.io/crates/jacquard) [![Documentation](https://docs.rs/jacquard/badge.svg)](https://docs.rs/jacquard) # 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](https://whtwnd.com/nonbinary.computer/3m33efvsylz2s) 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<'_>`](https://tangled.org/@nonbinary.computer/jacquard/blob/main/crates/jacquard-api/src/app_bsky/feed/post.rs) can borrow data (via the [`CowStr<'_>`](https://docs.rs/jacquard/latest/jacquard/cowstr/enum.CowStr.html) 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. ## 0.7.0 Release Highlights: - **Bluesky-style rich text support** - Parses from supplied text as well as explicit builder - Sanitizes input text - Also handles \[]() Markdown-style links - Optionally pulls out candidates for link/record embedding - Optionally fetches Opengraph link data for external links - **Moderation label application** - Generic implementation of atproto moderation/labeling client-side filtering/tagging via traits - Implementations for Bluesky and other types on best-effort basis - Demonstration options for use while avoiding Bluesky namespace or AppView infrastructure - **Websocket Subscriber-sent message control traits/code** - Primarily useful for Jetstream or other custom Websocket services - Fixed some `Data` value type deserialization issues > [!WARNING] > A lot of the streaming code is still pretty experimental. The examples work, though.\ The modules are also less well-documented, and don't have code examples. There are also a lot of utility functions for conveniently working with the streams and transforming them which are lacking. Use [`n0-future`](https://docs.rs/n0-future/latest/n0_future/index.html) to work with them, that is what Jacquard uses internally as much as possible. ### Changelog [CHANGELOG.md](./CHANGELOG.md) ## Goals and Features - Validated, spec-compliant, easy to work with, and performant baseline types - Batteries-included, but easily replaceable batteries. - Easy to extend with custom lexicons using code generation or handwritten api types - Straightforward OAuth - Stateless options (or options where you handle the state) for rolling your own - All the building blocks of the convenient abstractions are available - 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 - 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. ```rust // 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](https://tangled.org/@nonbinary.computer/jacquard/tree/main/examples) using `just example {example-name} {ARGS}` or `just examples` to see what's available. ## 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](https://img.shields.io/crates/v/jacquard.svg)](https://crates.io/crates/jacquard) [![Documentation](https://docs.rs/jacquard/badge.svg)](https://docs.rs/jacquard) | |`jacquard-common` | Foundation crate | [![Crates.io](https://img.shields.io/crates/v/jacquard-common.svg)](https://crates.io/crates/jacquard-common) [![Documentation](https://docs.rs/jacquard-common/badge.svg)](https://docs.rs/jacquard-common)| | `jacquard-axum` | Axum extractor and other helpers | [![Crates.io](https://img.shields.io/crates/v/jacquard-axum.svg)](https://crates.io/crates/jacquard-axum) [![Documentation](https://docs.rs/jacquard-axum/badge.svg)](https://docs.rs/jacquard-axum) | | `jacquard-api` | Autogenerated API bindings | [![Crates.io](https://img.shields.io/crates/v/jacquard-api.svg)](https://crates.io/crates/jacquard-api) [![Documentation](https://docs.rs/jacquard-api/badge.svg)](https://docs.rs/jacquard-api) | | `jacquard-oauth` | atproto OAuth implementation | [![Crates.io](https://img.shields.io/crates/v/jacquard-oauth.svg)](https://crates.io/crates/jacquard-oauth) [![Documentation](https://docs.rs/jacquard-oauth/badge.svg)](https://docs.rs/jacquard-oauth) | | `jacquard-identity` | Identity resolution | [![Crates.io](https://img.shields.io/crates/v/jacquard-identity.svg)](https://crates.io/crates/jacquard-identity) [![Documentation](https://docs.rs/jacquard-identity/badge.svg)](https://docs.rs/jacquard-identity) | | `jacquard-lexicon` | Lexicon parsing and code generation | [![Crates.io](https://img.shields.io/crates/v/jacquard-lexicon.svg)](https://crates.io/crates/jacquard-lexicon) [![Documentation](https://docs.rs/jacquard-lexicon/badge.svg)](https://docs.rs/jacquard-lexicon) | | `jacquard-derive` | Macros for lexicon types | [![Crates.io](https://img.shields.io/crates/v/jacquard-derive.svg)](https://crates.io/crates/jacquard-derive) [![Documentation](https://docs.rs/jacquard-derive/badge.svg)](https://docs.rs/jacquard-derive) | ## Development This repo uses [Flakes](https://nixos.asia/en/flakes) ```bash # Dev shell nix develop # or run via cargo nix develop -c cargo run # build nix build ``` There's also a [`justfile`](https://just.systems/) 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](https://img.shields.io/crates/l/jacquard.svg)](./LICENSE)