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.blogAug 24, 2026 at 4:54 AM
In Which A Book Lexicon is Born
Hi everyone, We recently held a sync to discuss creating a shared book lexicon for the Atmosphere Protocol. I’ve shared the full recording (thanks Ronen!) and notes from the meeting here: Fathom with some early notes here: https://app.notion.com/p/Book-Lexicon-Session-1-211b2b43aabb8007b098d063972ca58c (also do we have a ATProto version of Notion yet?) The book logging social scene is highly fragmented. Dozens of Goodreads alternatives are competing but not interoperating, leading to a lack of...
Lexicon Community
Lexicon Community is a shared space for general discussion of lexicons, lexicon design, and shared usage of lexicons.
Guidance on Authoring Lexicons
At last weekend's Atmosphere Conference, there were a lot of questions about how author Lexicons. I thought it would be a good idea to share some guidance.
Road to a book lexicon (Part 2) - Nick The Sick
The one where I actually define a lexicon
Two Types of Interoperability Without Sharing Lexicons - Wesley's notes
Sharing lexicons is not the only way to leverage atproto’s interoperability
Two Types of Interoperability Without Sharing Lexicons - Wesley's notes
Sharing lexicons is not the only way to leverage atproto’s interoperability
atproto made simple: publishing lexicons - underreacted
atproto made simple: publishing lexicons - underreacted
Wrote something that I'm down to talk more about #atprotonyc regarding book lexicons, having interoperable AppViews and getting to consensus for books. It's about the books, man!
A place of consensus making for the book lexicon — Olamaelcu
www.olamaelcu.netsay 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
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.devYeah I don’t totally understand why “just share a community lexicon” is not resonating for people. Can folks in this thread give feedback? discourse.atprotocol.community/t/shared-lexicons-messaging/6…
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
