Standard Reader

Nick's Blog

@ngerakines.me88readers32posts1mo ago

LatestRecent writing

Introducing attested.network: Proof of Payment for ATProtocol

attested.network is an open spec for decentralized proof of payments on ATProtocol, built on what we learned making atprotofans.com. It formalizes the three-party attestation model and opens it up for any app to implement.

atprotoattested.network

Signaling AI Preferences on ATProto

Atproto users need a way to express granular AI preferences and carve out exceptions for specific entities or content types. This post introduces community.lexicon.preference.ai, a lexicon schema that decomposes AI usage into distinct categories and adds a scoped override mechanism built on top of Bluesky's User Intents proposal.

atprotoLexicon Community

Payments on Protocol

atprotofans.com was a proof of concept for payments on ATProtocol built at Graze Social. This post is about what we built, why proof of payment on protocol matters, and what it makes possible.

ATProtocolatprotofans

Graze Social and the IETF

Graze Social sponsored my first in-person IETF meeting in Montreal last November. This post is about what it was like to be there and why standards participation matters for small companies.

If This Then AT: Automation on Protocol

IFTTA is an automation platform built on ATProtocol at Graze Social. It started as a hack-day idea and became a working system for event processing on protocol.

ATProtocolGraze Social

Building AIP: An ATProtocol Authorization Gateway

OAuth is the first challenge developers face in the atmosphere. This post is about AIP, the authorization gateway we built at Graze Social to alleviate some of the pain.

ATProtocolGraze Social

Spaces as Layers

Public anchor records paired with sidecar records in permissioned spaces give ATProtocol apps a composable pattern for blending open discoverability with controlled access.

ATProtocolpermission spaces

ATProtocol Patterns: Record Elicitation

Record elicitation is a pattern where a client asks an AppView to construct a record from the user's intent, rather than building it locally. This lets the AppView handle business logic, validation, and schema complexity while the client retains full authority over what gets written to the user's repository.

CIDs: What You Need to Know and Why, Part 2

How ATProtocol uses Content Identifiers to create a versioned, verifiable, and portable data model.

CIDs: What You Need to Know and Why, Part 1

A deep dive into Content Identifiers, the self-describing cryptographic fingerprints that form the foundation of ATProtocol’s data model.

B-Sides: Permissioned data is a love triangle

This is a B-sides post with unpolished thoughts that didn’t make it into the main article.

Permissioned data is a love triangle

Permissioned data is a love triangle between the user, the identities they grant permissions to, and the applications everyone uses to view controlled data. We don't need to change or reinvent the protocol to have it, because ATProtocol already supports it.