Jason Butterfieldjasonbu.onlineProjects built on AT Protocol
Author Commons is an AppView: a useful interface over portable identity, repository-owned publishing, and open conversation.
did:plc:72bi...5wpuio4vIndependent projects exploring portable publishing, identity, and durable public infrastructure.
Open project
Portable book and author metadata for the open web, designed so publishing context can move between compatible AT Protocol applications.
Essays, lab notes, and updates are written as Standard.site records.
collection: site.standard.documentrecords: 40latest: Sep 6, 2026
The record lives in my Personal Data Server. The site reads from there.
pds: woodear.us-west.host.bsky.networkdid: did:plc:72bi...5wpuio4vplacements: 30
Next.js renders a fast public interface from live protocol data.
renderer: Next.jssource: Standard.sitemode: public read
Readers discuss through AT Protocol clients. Conversation stays with identity.
threads: 3replies: 0portable: yes
lab
journey
lab
lab
From the field
Curated references I keep coming back to, each one an owned record in my repository. Protocol-native links stay live; the rest keep a captured snapshot.
ISBN's and the identity behind books is can not, as Nick identifies, be a unique identifier. We need another way to assign a book as a book. Editions throw a wrinkle into that and Nick and Bookhive gets around that with "Works" - still does not solve my issue of Authors without ISBN or a unique identifier.
Definitely an area I'm playing in. Looiking to develop Lexicons around my projects that can be adopted as a standard. Either that or augmenting existing lexicons, without just piling on. They need to be severable or new components of an exisiting Lexicon.
Getting to a common login and authorization that can be used on or off the AT Protocol network is key to growing the ATmosphere. Similar to the ubiquitous 'login with Google' button.