







say i was building something like goodreads on ATProto but ISBN doesn’t exist. is there an idiomatic way to handle public records in a shared way? i think i want both reviews _and_ books to be on the user’s PDS for true portability, but i also want books to be discoverable and have accurate info
Apr 19, 2026 at 6:29 PM
The Dissemination of Scholarly Information: Journals, Open-Access and Distributed Filtering
Current methods of disseminating scholarly information focus on the use of journals who retain exclusive rights in the material they publish. Recently there has been increasing dissatisfaction with this model, with suggestions for alternative approaches such as "Open Access".
Introductions and kick off
Hello, I’m Simon Horrobin. I’m working on a couple of projects which are ATproto relevant… one to handle sport and health data, the other for managing publishing workflow. Both of these need privacy to varying degrees. I think about this in a few axes… who can create, view, edit, delete, grant, revoke, all over time and state.

Publishing · Standard Reader
Wire a personal site's own site.standard.* records by hand.
Representing groups in ATProto
I wanted to add book clubs to my GoodReads-like app (Collective), but ATProto doesn't have a standard way to handle shared group resources yet. So I'm building opensocial.community—a separate service that manages groups independently from any single app. This means the same book club could potentially work across multiple apps (imagine your book club having both a reading list in Collective AND a discussion forum in another app), and groups can migrate between providers if needed. It's probably over-engineered for my use case, but might help other ATProto developers building community features.

Representing groups in ATProto
I wanted to add book clubs to my GoodReads-like app (Collective), but ATProto doesn't have a standard way to handle shared group resources yet. So I'm building opensocial.community—a separate service that manages groups independently from any single app. This means the same book club could potentially work across multiple apps (imagine your book club having both a reading list in Collective AND a discussion forum in another app), and groups can migrate between providers if needed. It's probably over-engineered for my use case, but might help other ATProto developers building community features.

From Albums to Streams: How Modularity Changes Systems
Scientific publishing is breaking under document-centric formats designed for a physical world. Borrowing from music’s shift from albums to streaming, we make the case that open access alone cannot deliver reuse, trust, or scale. The future of science depends on modular, interoperable research components that move across tools, enabling new workflows, tools, and ecosystems.
The Cypherpunk Library
A personal collection of good public-domain reads. Free to read, free to keep.

FeatherReader — read, quietly
Subscriptions, folders, stars, and read-state are written as open-standard community.lexicon.rss.* records in your atproto PDS — portable to any reader that speaks the lexicon. Leaving is as easy as arriving.
Three schemes for shared-private storage - Paul's Leaflets
This is definitely the sort of thing that I have in mind with book interop. The reality is that with so many data sources for books, that there needs to be some sort of mapping of books, which would need the user to explicitly decide on the mapping.
Wesley Finck
after a fun chat with @laurenshof.online and @ronentk.me I finally made time to write up some more thoughts about interoperability in the atmosphere without needing to share lexicons! notes.wesleyfinck.org/3maq3h26ook2h
At Side Project Saturday (hosted by @val.town) I demoed a bookmarking service I'm building to learn more about ATProto and user-owned data. I've a bit stuck on bookmark lexicons and what belongs in a record. Thx to @awarm.space for suggesting I write down my questions donohoe.dev/2026/bookmark-lexicons-atprot…
What Is a Bookmark?
donohoe.devBeen thinking about what digital ownership could look like on atproto: NOT NFTs/speculation, but real transferable digital objects. An album, artwork, book, etc. with its own DID, provenance, rights, lending, gifting & resale. Access is a service; ownership is an object. PDS to PDS transfer.
I've been thinking a lot about how to define a shared book lexicon for the Lexicon Community Working Group: discourse.atmosphere.community/t/in-which-a-book-lexicon-is-… But, instead wrote a treatise against ISBNs. I hope I can link to it whenever someone asks why their import didn't work on @bookhive.buzz 😝
Road to a book lexicon (Part 1) - Nick The Sick
nick-the-sick.pckt.blogEmerging from being "down in the technical weeds" of #atproto is a little mashup of @semble.so & WayFinder (wayfinders.network) Semble team released "open collections" this week - here we explore the "private & permissioned data" collection, created by @bmann.ca & now with 3 other contributors
What's the intended app/user etiquette for atproto apps with regards to publishing to the same lexicon? Like, say I build an atproto app, would it catch users by surprise if the wrote to the same records (e.g. posts, likes, etc?) that show up in the bsky.app? Or should my app be isolated?