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

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

We have selected the designer to work on this project. We are in touch with them and we'll kick it off in August. Thanks to all the designers who applied 🙌 bsky.app/profile/ther...

Hugo@there-hugo.dev · 3w ago

Call for designers: Lexicon Community logo Last day to apply discourse.atprotocol.community/t/call-for-d...

The smallest permissioned data shape: a bookmarks space with a member list that never grows past me. Same bookmark record the atmosphere already uses, same write path, different address. URIs, scopes, tokens, and the full credential flow inside.

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.

ngerakines.leaflet.pub

Tuesday, July 14th is @smokesignal.events's 2 year anniversary! Join me along with some special guests at 11:00 AM eastern on @stream.place to celebrate two years of atproto firsts and talk about what's next for one of the atmosphere's first apps!

Two Year Anniversary

This is the two year anniversary of the launch of Smoke Signal! Live stream starts at 11:00 AM (Eastern / New York) at https://stream.place/ngerakines.me!

atmo.rsvp

✅ community.lexicon.app.defs ✅ community.lexicon.app.entry ✅ community.lexicon.app.profile ✅ community.lexicon.app.profileLocalization

community.lexicon.app.profile Documentation (EN)

The canonical self-published profile for an app built on or for the AT Protocol.

lexicon.garden

A proposal for the "community.lexicon.location.place" lexicon schema by @schuyler.info. If you're interested in the location and geo lexicons, please give it a read and review. github.com/lexicon-comm...

Proposal: Lexicon and documentation for community.lexicon.location.place by schuyler · Pull Request #64 · lexicon-community/lexicon

Here's a proposed lexicon for geographic place information, which builds on the existing community.lexicon.location.* types, and adds conventions for globally unique identifiers, naming schemes...

github.com

👋 @hipstersmoothie.com, your feedback was requested on this PR. Can you add it to your queue? github.com/lexicon-comm...

Add community.lexicon.app lexicons by pixeline · Pull Request #76 · lexicon-community/lexicon

Summary Adds the app directory proposal from the Community App Lexicon WG thread: community.lexicon.app.entry for community/third-party app listings community.lexicon.app.profile for official self...

github.com

PR up for review. One approval by @ngerakines.me. If you have questions or feedback, please submit it.

Tyler Fisher@tylerjfisher.com · 3mo ago

Based on my proposal from a couple weeks ago, I submitted a PR to the community lexicon repo for bookmark permission sets: github.com/lexicon-comm... There are machine translations for the top 5 languages on Bluesky in here, would love if anyone could help verify that they read correctly!

Our MCP will now respect these settings. If inference is off, it shouldn’t access your data.

Rude1 Haunted Badness. ⁂@rude1.blacksky.team · 3mo ago

ICYMI: We have a new "AI Preferences" setting This allows you to announce to the entire ATmosphere network what you consent to regarding AI use of your public data. Other apps can see this but ~may not~ respect the settings We built this to give you a place to set these and will 100% respect them

🎉🎉🎉

Rude1 Haunted Badness. ⁂@rude1.blacksky.team · 3mo ago

ICYMI: We have a new "AI Preferences" setting This allows you to announce to the entire ATmosphere network what you consent to regarding AI use of your public data. Other apps can see this but ~may not~ respect the settings We built this to give you a place to set these and will 100% respect them

The @lexicon.community welcomes discussions and questions in the forum discourse.atprotocol.community/c/lexicon-co... You can also literally explore lexicons with @lexicon.garden lexicon.garden

Today we swapped out Sifa's custom location type for @lexicon.community's community.lexicon.location.address, the shape @smokesignal.events and others already use We use this for both account locations, and locations for career and education items (all optional of course). #interop

a man in a black shirt with the words swap it like it 's hot on it

Alt: a man in a black shirt with the words swap it like it 's hot on it

media.tenor.com

Are you building on atproto? Wanna join a working group for a @lexicon.community lexicon that would allow users to express their consent in AI usage? Please join the conversation below I plan to do this in the blacksky.community settings to let users opt out of AI. It'd be better to interoperate.

The community.lexicon.preference.ai lexicon

Hey everyone, Picking up from a few weeks ago, I created a PR that I’d like comment on. I’m specifically looking for who would be interested in using this lexicon to interop:

discourse.atprotocol.community

New blog post: Signaling AI Preferences on ATProto. Introducing community.lexicon.preference.ai, a lexicon for granular AI data usage preferences with scoped overrides for specific entities and collections. #AI #atproto

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.

ngerakines.leaflet.pub

A PR to introduce the community.lexicon.preference.ai lexicon has been created. github.com/lexicon-comm...

Add community.lexicon.preference.ai lexicon by ngerakines · Pull Request #72 · lexicon-community/lexicon

Summary Introduces the community.lexicon.preference.ai lexicon for declaring user preferences regarding AI usage of their public data Decomposes AI usage into four distinct categories (training, i...

github.com

Rude1 Haunted Badness. ⁂@rude1.blacksky.team · 4mo ago

Suppose a Bluesky user does not want any of their public data to be used for generative AI training. They would go in to app settings, find the data reuse preferences section, and configure “Generative AI” 🤖 to “disallow” 🚫. The app would create this public record in their repository:

📣 Hey, listen! The new home for Lexicon Community discussions is here: discourse.atprotocol.community/c/lexicon-co...

Forum Changes - READ THIS

Hello everyone, The new home for Lexicon Community discussions is here: https://discourse.atprotocol.community/c/lexicon-community/31/none This forum will be in read-only mode to give people time...

discourse.lexicon.community

alright woohoo, it's deployed and uses oauth! not bad for a weekend hack :) it's basically a minimum viable bookmark manager. it saves to your pds using the lexicon.community bookmark check it out, bookmarks on the atmosphere: boomarks.netlify.app please help me come up with a better name 😂

Recently there has been a lot of dividing & heated discourse about ActivityPub and AT Protocol. Yesterday at the Social Web CG meeting, I proposed releasing a statement on this discourse, you can read the full statement here: github.com/swicg/genera... #activitypub #atprotocol #atproto #SocialWeb

🔒 Our discourse instance has been updated to use ATProtocol OAuth scopes. We can all sleep a little better at night, knowing that the next discourse 0-day won't destroy your repository and identity.

♨️ Attention ♨️ We're moving away from GitHub discussions to Discourse! This is the best place for long-form discussion about lexicons, how they're crafted and used, and what belongs in the Lexicon Community portfolio. See you there!

Lexicon Community

ATProtocol developers working on lexicons

discourse.lexicon.community

👀

fig (aka:[phil])@bad-example.com · last yr.

it's a good atproto day ufos.microcosm.blue

Started a discussion about adding header images to Lexicon Community defined events. #atdev #lexicons #atprotocol

Event header images

Hello! @ngerakines.me from https://smokesignal.events/ here! I’d like to propose some changes to the community.lexicon.calendar.event record type to support header images. Specifically, I’m proposi...

discourse.lexicon.community

Updated the website a bit to talk about the custom #atgeo checkin record I made for Anchor dropanchor.app the latest app version uses a very lightweight custom pds to store these check-ins and serve them to clients.

Please join us in welcoming @bsky.app to the Lexicon Community Technical Steering Committee! We’re excited to partner in shaping the AT Protocol Lexicon and supporting healthy, vibrant developer communities.