Skip to content

Standard Reader

Nick's Blog

158Readers

41Posts

23d agoLast active

Permissioned Data: Space Access

Stepping outside the shapes series for a deep dive: how space configuration decides which people and which apps get credentials. Here be dragons.

atprotopermissioned-data

Permissioned Data Shapes: Notifications

A self-keyed space gives notifications a home you control: every app gets an append-only sink to write into, you pick the reader that turns them into pushes and emails, and allowing or revoking an app is an access control you already have.

atprotocolpermissioned-data

Permissioned Data Shapes: Feeds

Public feed generators drink from a firehose that permissioned data never enters, so a feed that includes space content has to become a syncer, keep a live model of who can see what, and serve a different skeleton to every viewer.

atprotopermissioned-data

Permissioned Data Shapes: Polls

A poll is a space, a ballot is an address, and read_self is the ballot screen: voters cast and change their own votes while no voter's client can read anyone else's.

atprotopermissioned-data

Permissioned Data Shapes: Forums

A forum with public categories, private categories, and one set of record shapes across both: members own their posts, the forum owns the submission wrappers that admit them into categories, and moderators deactivate into tombstones instead of deleting.

atprotopermissioned-data

Permissioned Data Shapes: Community-Moderated Content

A community can own spaces the way a person does: a club's members post to each other under a dedicated community DID, with a feed space for content, a moderation space for notes, a labels space for filtering, and a single app view as the only window into any of it.

atprotopermissioned-data

Permissioned Data Shapes: Private Events

atprotopermissioned-data

Permissioned Data Shapes: Self-Only Bookmarks

A self-only space is the smallest shape permissioned data can take: one authority, one member, one repo, and private bookmarks that share a record shape and a write path with public ones.

atprotopermissioned-data

Reading Proposal 0016: What atproto’s “Permissioned Data” Actually Does

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