We’re about to start building recurring events for Roundabout, but before we do, I’d love to tap into the collective wisdom of the atproto community. Our existing events are stored as community.lexicon.calendar.event records. Those records don’t capture necessary information about event recurrence, so we’ll need to either extend the lexicon or use sidecar records. The data that we want to store is relatively complex. RFC 5545 is comprehensive on what recurrence rules we might want to support[1...
Event Aggregator
Hi there 👋 There’s no good one-stop shop to find all the various events happening in a given city, so I’m trying to build one! I’ve got a fairly basic implementation up here. At the moment, it just runs a daily cron that scrapes events from a small set of local Vancouver publications/venue websites then pushes them to a bluesky collection, which the site then fetches and uses to populate the calendar. It supports basic commenting and RSVP functionality via bluesky auth. It’s very...
Bitesize Proto: Upserting ATProto Records - Hitchhiker's Guide to the Atmosphere
Tired of creating duplicate records in a repo from your atproto app?
Transmogrify Record - Lexicon Garden
Transform records between ATProtocol lexicon schemas
AT Protocol Development, Tech Talks, and Events
Exploring CRDT Lexicons
I’ve (alongside many others I’m sure) been working on CRDT work with atproto, and I think we’ll need to come up with some standard for how to represent CRDT data as lexicons. @chris.pardy.family has written a leaflet exploring what such a record could look like and is looking for feedback and thoughts: CRDT's on ATProto I think it’s a good start. It doesn’t tie us to any particular CRDT, though it doesn’t guarantee interop between different CRDT types, which seems fine to me. I’m thinking may...
calendar pt. 1: ATProtocol beyond AppViews - building [at] habitat
our approach to permissioned data (part 1!)
The Rules of Recurring Payments: Every Constraint Has a Story - ATProtoFans Blog
Part 2 of our "Building Recurring Payments in Public" series where we give some context the behaviors, constraints, and definitions of recurring payments.
Atproto Amsterdam Lookbackforward
Event report and future ideas for Atproto community in the Netherlands, written up by @burrito.space
Linked — watch ATProto links in real time
See which records across the atmosphere point at an ATProto account, with history from Constellation and live events from Spacedust.
Labeler Relay
A tool for finding atproto labelers, aggregating their data, and rebroadcasting a unified event stream.
We've converted all the talks to atproto records using the @lexicon.community events format, owned by the @atmosphereconf.org account You can search and RSVP to talks wherever you get your events e.g. smokesignal.events/did:plc:3xewinw4wtimo2lqfy5fm… or atmo.rsvp/p/atmosphereconf.org
I'm going to "Lexicon Community Monthly Meeting — October 2026".
Lexicon Community Monthly Meeting — October 2026
atmo.rsvpI wrote my first #atproto community discourse topic. Pretty simple idea, but can be a good groundwork for private data, group-owned data or off-protocol data.
[Proposal] AT-URI for cross-service records
discourse.atprotocol.community@eagraf.dev with part 1 of how we're building a personal calendar on ATprotocol and what we're thinking about (differently!) for permissioned data
calendar pt. 1: ATProtocol beyond AppViews
habitat.leaflet.pub
