Lightweight Universal CIDs
CID Congress #2 · Luma
This is the 2nd in a series of working sessions towards making CIDs & content addressing easier to use: more deterministic, better compatibility, leaner…
CID Congress #3 · Luma
This is the 3rd in a series of working sessions towards making CIDs & content addressing easier to use: more deterministic, better compatibility, leaner…
trueberryless/awesome-atproto
A curated, auto-updating list of awesome resources, apps, libraries, and developer tools for the AT Protocol (atproto).
atproto-crates — AT Protocol building blocks for Rust
A Rust workspace of eighteen crates for AT Protocol: content addressing, DID and handle resolution, repositories and Merkle Search Trees, OAuth with DPoP, XRPC services, and event streaming.
tapped: a Rust crate for building ATProto appviews with tap
Crates.io: https://crates.io/crates/tapped GitHub: https://github.com/thombles/tapped
Heron - A gentle atproto client
Heron - A gentle atproto client
I just rewrote llama.cpp server in Rust (most of it at least), and made it scalable
497 votes, 46 comments. Long story short, I rewrote most of the llama-server, made it scalable, and bundled that into Paddler. Initially, the project…
CIDs: What You Need to Know and Why, Part 2 - Nick's Blog
How ATProtocol uses Content Identifiers to create a versioned, verifiable, and portable data model.
The ATProto community built a ton of great features and products over the past year. For our next trick, let's mature them into products and businesses.
Mosh Lee
(2/n) A feature solves one problem well — even delightfully well. But features get copied easily or absorbed into larger products. They have no distribution or adoption model. If your whole thing can become a pane in someone else's app, it's a feature.