Back to 2301 Classroom10:30 AM - 11:00 AM PDT
Did Lexicon just accidentally solve the enterprise data problem?2301 Classroom · Conference Day #1

One of the core ideas behind the Data Mesh architecture is that data products should be decentralized and domain-oriented. The main barrier to successfully implementing Data Mesh is that decades of data tooling have assumed that data governance and engineering teams are centralized. ATProto’s Lexicon data definition language, however, deftly balances both the “nouns” and “verbs” of data modeling, making it a promising candidate for implementing a decentrally-managed data architecture.

Attendees
JauntyWunderKind avatar
David VdB avatar
Ashlynne avatar
Seth avatar
Steve Layton avatar
Hilary Baumann 💻 🥃 avatar
Bryan (they/them) @ atmosphereconf avatar
Paul Frazee avatar
Emelia avatar
Patrick Singletary avatar
Daz avatar
taurean avatar
mohr26.bsky.social avatar
Joe Germuska avatar
flo-bit avatar
Ranga Krishnan avatar
fig (aka:[phil]) avatar
Christian avatar
Silvern Skye  avatar
bryan newbold avatar
dad (aka miguel) avatar
Victoria avatar
Evan Jarrett avatar
More from this room
OAuth Masterclass
9:30 AM - 12:30 PM
Abstracting the Appview Workshop
2:00 PM - 4:00 PM
Chad's workshop dives into AppViews, what they are, how they work, and the different ways to implement them. He'll explore how tools like quickslice can abstract away the complexity so you can stay focused on your Lexicons and UI/UX. We'll also look at additional tools, including Tap, AIP, Constellation, and more, covering approaches from getting started all the way to production. Bring your questions. Many answers are 'it depends', shaped by your specific product and Lexicon design.
Verified Human Users, game changer in the atmosphere
4:00 PM - 5:00 PM
Bots are swarming on most social media, and dominating in some. Social media has become asocial. How can we bring sanity and social exchange back again? W Social makes a strong bet on verified human users, meaning passport scanning in order to get a W Social account. But do we always want to know who is behind every account? We propose a model with a user information firewall. One side knows exactly who each user is, but not which social media account belongs to her. The other knows everything about the user's friends, likes and followers, but not her true identity.
Consuming the ATmosphere
9:30 AM - 12:30 PM
This will be an introductory workshop for developers who may have some JS/TS experience but almost no AT experience, who want to learn how to read posts and other data from the Atmosphere.