Tessera

Inlay

@inlay.at

social components

16 Posts579 Follower 1 Folgt

dan @danabra.mov · 4mo ago

my talk about @inlay.at is up! it’s a messy whirlwind tour of the rabbithole i spent the last two months in: remixable social UI components that live directly on the AT protocol

Social Components - ATmosphereConf 2026

YouTube video by AT Protocol Development, Tech Talks, and Events

youtu.be

Inlay @inlay.at · 4mo ago

fixed an issue that borked "create lexicon" modal (which shows up if you click the scroll-like icon in the topbar). publishing component lexicons directly through inlay should work now

lexicon modal with a publish button

Inlay @inlay.at · 4mo ago

we're seeing another issue where dynamic endpoints come back with an error — we're running into @val.town usage limits looking into ways to resolve that

Inlay @inlay.at · 4mo ago

looking into it!

Gov@gov.glados.computer · 4mo ago

Looks like @inlay.at got hug of death'd?

Inlay @inlay.at · 4mo ago

today was the Inlay release day! discover, remix, create, and compose different ways to view the Atmosphere data on inlay.at

Inlay @inlay.at · 4mo ago

tomorrow

dan@danabra.mov · 4mo ago

my talk about @inlay.at is tomorrow! i'm also optimistically hoping to actually deploy and open source it by then rsvp if you want:

Inlay @inlay.at · 5mo ago

aaaaaand we have documentation! tangled.org/danabra.mov/...

danabra.mov/inlay

social components

tangled.org

Inlay @inlay.at · 5mo ago

first public prototype! this ui is made entirely out of at:// components inlay-proto.up.railway.app

dan@danabra.mov · 5mo ago

first pieces of @inlay.at are now open source at tangled.org/danabra.mov/... 🔮 Inlay "browser" prototype (hono+htmx): inlay-proto.up.railway.app 📝 Inlay ProfilePage component from the above demo: pdsls.dev/at://did:plc... 📜 Tests describing the Inlay rendering model: tangled.org/danabra.mov/...

// ============================================================================
// inlay render — specification tests
// ============================================================================
//
// inlay is a UI component system on the AT Protocol.
//
// Elements reference components by NSID — <com.example.PostCard uri="...">
// is an element whose type is the NSID com.example.PostCard. An NSID is
// just a name; it says nothing about where the implementation lives.
//
// A pack (at.inlay.pack) maps NSIDs to concrete implementations. Each
// entry points an NSID at a component record URI (at://did/at.inlay.component/rkey),
// so the same NSID can resolve to different implementations depending on context.
//
// A component record (at.inlay.component) defines what happens when the
// element is rendered. It has one of three body kinds:
//
// - no body → a primitive; the host knows how to render this
// - bodyTemplate → a stored element tree with Binding placeholders
// - bodyExternal → an XRPC endpoint that returns an element tree
//
// Resolution algorithm:
//
// 1. Start with an element like <com.example.PostCard uri="at://...">.
// 2. Scan imported packs for a component that implements com.example.PostCard.
// 3. Resolve the component record and switch based on body kind:
// a. no body → done, it's a primitive.
// b. bodyTemplate → substitute Binding placeholders with the
// element's props (and optionally a fetched record when the
// component declares that it's a "view" for some records).
// c. bodyExternal → call the XRPC service, passing props.
// Children can be passed too, but they're opaque to the callee.
// 4. Recurse into the expanded tree until everything resolves to
// primitives. This can be done to completion or (better) streamingly.

Inlay @inlay.at · 6mo ago

same <List>, different layouts

Inlay @inlay.at · 6mo ago

first pass at embeds

Inlay @inlay.at · 6mo ago

let’s make a profile page

Inlay @inlay.at · 6mo ago

hello world