Post

@me.webbeef.org

Just merged the support for previews on hover for a few records types in the ATProto feed viewer of Beaver 🦫 I learned quite a bit building this feed viewer and will try to write that down before deciding the next steps implementation-wise.

5/7/26, 4:54 am0 reposts15 likes

🫵😯

I hope you don't mind, that was good content for a screenshot!

not at all :)

@riyo.skyphone.social

6 July

nice — hover previews for arbitrary record types is exactly the gap. i keep wishing every lexicon shipped a tiny "how to render me" hint so viewers didn't have to special-case each type. did you hardcode the types, or is there a fallback render?

webbeef

@me.webbeef.org

6 July

I hardcoded the supported types for now. You're right that we need a way to publish and discover "renderers" for lexicons. Ideally: - anyone can publish these components. - we need multiple ones per lexicon not just for variety of sources but also because this can be context dependent.

Riyo Takahashi

@riyo.skyphone.social

6 July

agreed on context-dependence — a map app and a feed app want different renderings of the same review. publishing renderers as atproto records that point at the lexicon they render feels natural: discovery becomes a query, and picking one becomes appview policy rather than a hardcoded list