Lexicon Community

@essentialrandom.bsky.social published a survey of sidecar record patterns in AT Protocol, plus a proposed #4 for schema-defined extension fields in records. Check it out!

@bradestey.com launched sequential.work — a standard.site-inspired comics lexicon on Tangled, covering webtoon, paged, and strip formats. blampow.app beta is open for indie creators.

@bnewbold.net raised the question of shorter NSID domains for future community lexicons. @bmann.ca confirmed the org is working on a process for new domains. Join the discussion on Discourse.

TSC recap: @essentialrandom.bsky.social is sponsor for the images lexicon. @bmann.ca has a Cheese Community co-lead. New logo! Service self-description has live implementations. Full notes: blog.lexicon.community/a/3mwvtlrid2t23-october-2026-meeting

Daniel Holmgren's (@dholms.xyz) FediForum talk on AT Protocol Spaces is now available. Covers permissioned spaces, DPoP+ath tokens, and space-scoped addressing - the core infrastructure behind the next wave of apps building on the atmosphere.

@edouard.paris and @viivi.rocks are submitting the AT Protocol devroom proposal for FOSDEM 2027 — tomorrow is the deadline. If you've been thinking about a talk, project demo, or use case, now is the moment to get in touch and help shape the AT Proto track in Brussels.

Governed crossing lexicon draft - data from personal infra into shared systems. Access-change events, agent grants, conformance rules. Through Oct 26. https://discourse.atmosphere.community/t/lexicon-draft-for-feedback-recording-access-changes-in-governed-crossing-records-open-until-26-oct/1287

Raise your hand if you want to see non-Bsky lexicons on Bluesky. @bookhive.buzz @standard.site @lexicon.community

New logo, who dis?

Tomorrow: Lexicon Community TSC meeting, Thursday October 1 at 1:00 PM ET / 17:00 UTC. WG updates, domain stewardship discussion, and community Q&A. Reply to the thread on Discourse to request the join link.

@tynanpurdy.com published a detailed design for a general-purpose ratings lexicon set under community.lexicon.rating.*: scale, prompt, and rate records covering nominal, ordinal, interval, and ratio levels. With examples from Netflix scales to iFixit repairability. Feedback welcome on the thread.

jediwright.com shared a draft of governed crossing lexicons for recording when data crosses from private systems into shared infrastructure. The first draft covers access changes: gate checks, effect observations, and publication rules. Four design questions open for feedback until 26 Oct.

@byjp.me's deeplink lexicon proposal has been collecting rich design input since May: nicr.dev's at-templates (Igalia), @bnewbold.net's project-declaration framing, dame.is's aturi.to, and Nick's Hopper POC — converging on how AT Proto records bridge to web apps. Join the discussion on Discourse.

@bnewbold.net contributed design feedback on the file sharing lexicon — referencing git-annex special remotes and WebTorrent as prior art, and suggesting thumbnail blobs, additional hash types for cross-database compatibility, and appview-side proxying for bandwidth distribution.

Three days out: the Lexicon Community TSC meeting is this Thursday, October 1 at 1:00 PM ET / 17:00 UTC. Book WG, image lexicon convergence, location OSM integration, Cheese Community stewardship, and namespace policy updates on the agenda. Request the join link on Discourse.

@gui.do shared detailed schema suggestions for the /now lexicon - proposing optional 'url', 'summary', and 'updatedAt' fields to bridge web AT Protocol publishing. The discussion is converging on practical design. Schema feedback welcome on the thread.

@norman.life built ATFISL — a download-location lexicon for AT Protocol keyed by file CID. Multiple URL schemes per file, per-URL expiry, content-addressed identity. Complements FISL, a query interface for aggregating locations across the network. Feedback welcome.

Heads-up: the next Lexicon Community TSC meeting is Thursday, October 1 at 1:00 PM ET / 17:00 UTC. Agenda topics welcome in the discussion thread on Discourse.

@bmann.ca has a co-lead for Cheese Community — a learning WG exploring lexicon creation and canonical data on AT Protocol. The cheese.community domain transitions to Lexicon Community stewardship as a governance test case. Details on Discourse.

@tynanpurdy.com is asking whether AT Protocol lexicons should share a common type for BCP-47 language tags, so schemas can reference it instead of each defining their own `langs` field. Join the discussion on Discourse.

@tynanpurdy.com proposed a community.lexicon.rating lexicon for universal ratings — a shared way to represent star, numeric, and qualitative scales across AT Protocol apps. Read the full writeup and share feedback on Discourse.

A community proposal for a `community.lexicon.download` or `community.lexicon.file` lexicon is open for discussion -- file sharing with multi-method distribution (PDS blobs, IPFS, BitTorrent). @nezumi.eurosky.social is seeking collaborators. Share your feedback on Discourse.

The FOSDEM 2027 AT Protocol devroom proposal is taking shape. @edouard.paris and @viivi.rocks are leading the submission, due October 4. The draft covers protocol infrastructure, applications, governance, and critical perspectives. Share project ideas and use cases in the Discourse thread.

Book WG momentum: @nickthesick.com submitted a PR on BookHive with proposed lexicons for book editions and standalone reviews — splitting edition data from reviews into distinct namespaces. The path to community.lexicon.* publishing: a Tangled registry PR is next. Join the discussion.

The AT Protocol Permissioned Data spec (0016) has been updated - introducing Spaces, app-scoped permission sets, DPoP+ath bound tokens, and TID-space-creation records. A significant architecture milestone for the ATmosphere. Track the work across PRs #100 and #101.

@byjp.me shipped isnot.at - a live demo of the is/not micro-review lexicon for AT Protocol. Reviews are thumbs up/down with optional +/- 2 extremes. Published at at.isnot.review on lexicon.garden with cross-app integration via panproto.dev lenses.

The community is shaping an AT-URI deeplink lexicon - a standard way to connect websites back to AT Protocol records. @jvuillermet.eu's custom AT Proto feed is built for it; @byjp.me's isnot.at cross-references the same pattern. Add your perspective on Discourse.

@trezy.codes shared how HappyView detects PDS spaces support — checking community.lexicon.service.describe first, with a fallback for PDSes without it yet. The question: what would a better detection standard look like? https://discourse.atmosphere.community/t/detecting-spaces-support/1261

The next Lexicon Community TSC meeting is Thursday, October 1 at 1:00 PM ET (17:00 UTC). Agenda topics welcome — join the discussion thread to propose items or follow along.

@tynanpurdy.com proposed a new /now page lexicon on Discourse — now.nownownownow.entry, inspired by Derek Sivers' nownownow movement. Seeking a co-lead for the working group. Schema discussions underway with chadkoh.com and caesar.dev on slashpages integration. Join the thread.

Our monthly Lexicon Community TSC meeting is today at 1:00 PM ET / 17:00 UTC. Agenda: lifecycle for published lexicons, TSC role and identity, and governance restructuring follow-up. Details and RSVP on Discourse.

New voices joined the community.lexicon.media.image discussion on Discourse - byarielm.fyi, essentialrandom.bsky.social - helping converge on alt text as a language-tagged array, a sidecar pattern for licensing and copyright, and consistent aspectRatio. Schema taking shape with 10+ contributors.

The community.lexicon.book working group is taking shape. 10+ builders from Bibliograph, BookHive, Dracome, Hardcover, and Byline are at the table hashing out works, editions, progress, and discovery. A dedicated forum category is on the way. Jump in on Discourse.

Okay, we're over the hill now, once @latr.link comes back up, we'll be live with the `community.lexicon.bookmarks.bookmark` lexicon from @lexicon.community

✅ @lexicon.community has been verified by @bsky.app.

This is what I recently did with my `one.youronly.rsc.images` lex, uploading standalone images that I can easily access and copy-paste. 😅

Hey @luke.kanies.com - I have this work in progress @cheese.community lexicon that I just posted as sort of a learning exercise for @lexicon.community discourse.atmosphere.community/t/cheese-com... Looking at it again and your universal reviews, I think we can do this with an open union?

@natespilman.at has proposed community.lexicon.media.image — a standalone image record lexicon for the ATmosphere, independent of any embed context. Luminframe, Grain, and others are at the table. @al9000.com has offered to co-lead. Join the discussion on Discourse.

Working group forming around community.lexicon.book — a shared book lexicon for the ATmosphere. @omg.jacky.wtf, @adamfortuna.com, and @jasonbu.online are building across Bibliograph, BookHive, Hardcover, and Byline.pub. Gather builders, find primitives, ship a v0. Join the Discourse thread.

Governance you can diff: the governance model, contributor covenant, and contributing guide live on the website with effective dates and changelogs, so you can see how the rules have changed over time. https://lexicon.community/governance/

Notes from the August 2026 TSC Meeting are available on our blog. #offprint

📅 Our next monthly meeting is Thursday, September 3 at 1 PM ET / 17:00 UTC. Agenda (so far): published-lexicon lifecycle, TSC role discussion, governance restructuring follow-up.

Our code lives on @tangled.org. Another on-protocol choice: Tangled is built on AT Protocol, so our repositories belong to our identity, not to a platform account. One more piece of Lexicon Community in the atmosphere, one step closer to 100%. https://tangled.org/lexicon.community

The Lexicon Community blog runs on @offprint.app. We chose it because it's built on AT Protocol: our posts live in the atmosphere, right alongside the schemas they describe. One more piece of Lexicon Community on-protocol, and one step closer to 100%. https://blog.lexicon.community/

The community.lexicon.* schemas have a new home: development happens at https://tangled.org/lexicon.community/lexicons, and the published records live on @lexicons.lexicon.community, a dedicated identity that holds the schema records and nothing else. Same NSIDs, same records, sturdier plumbing.

Have a lexicon you wish existed? The new design guide walks the whole path: start from a real-world use case, form a working group (anyone can), design in the open, and land it through TSC review. https://blog.lexicon.community/a/3mrnjm3br7723-how-to-design-a-lexicon-community-lexicon

How does an NSID like community.lexicon.calendar.event resolve to a schema? DNS names the authority, a DID locates the repository, a record holds the schema. We wrote up the whole chain, including how to verify it offline: https://blog.lexicon.community/a/3mrnjw6qzzq23-publishing-and-resolution

We just finished a restructuring. The website is now the source of truth for governance, the schemas moved to Tangled, NSID resolution got a dedicated identity, and the process is lighter. The story is on the new blog: https://blog.lexicon.community/a/3mrlquupo2a23-reintroducing-lexicon-community