Hackers' Pub

Syntax	Description	Examples
`"` keyword `"`	Finds the string within quotes, including spaces. Case-insensitive. (Escape quotes inside with `\"`)	`"Hackers' Pub"`
`from:` handle	Finds content written by the specified user.	`from:hongminhee` `from:hongminhee@hollo.social`
`lang:` ISO 639-1	Finds content written in the specified language.	`lang:en`
`#` tag	Finds content with the specified tag. Case-insensitive.	`#HackersPub`
condition condition	Finds content that satisfies both conditions on either side of the space (logical AND).	`"Hackers' Pub" lang:en`
condition `OR` condition	Finds content that satisfies at least one of the conditions on either side of the OR operator (logical OR).	`#HackersPub OR "Hackers' Pub" lang:en`
`(` condition `)`	Combines the operators within the parentheses first.	`(#HackersPub OR "Hackers' Pub" OR "Hackers Pub") lang:en`

dan @danabra.mov@bsky.brid.gy

2/25/2026, 5:30:40 AM

Public

first pieces of @inlay.at@bsky.brid.gy 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.

If you have a fediverse account, you can quote this note from your own instance. Search https://bsky.brid.gy/convert/ap/at://did:plc:fpruhuo22xkm5o7ttr2ktxdo/app.bsky.feed.post/3mfnxazonqc27 on your instance and quote it. (Note that quoting is not supported in Mastodon.)