Skip to content

Commit bfabef4

Browse files
ralyodioclaude
andcommitted
blog-post: let a post say who wrote it, in a form a machine can read
A post already carries the byline in prose -- "by Anthony 'chovy' Ettinger" -- which is exactly the form nothing can act on. Directories, feed readers and the fediverse all look for `rel="me"`, and the template published none, so a crawler could tell you the post existed and nothing about who to reach about it. Concretely: rssamplifier indexed this blog, found the author's name from the feed's managingEditor tag, and shipped an author page carrying an email and a GitHub link and nothing else -- because the pages genuinely declared nothing else. The only outbound links on the whole blog were two to kagi.com. `rel="me"` is the strongest evidence an identity extractor has, ranking above h-card, JSON-LD `sameAs` and ordinary footer links, because it is the one a publisher has to state deliberately. Verified against rssamplifier's own `identityFromHtml`: all three links come back as `source: "rel-me"`. Personal accounts only. The company's X and YouTube accounts are deliberately absent -- a directory that files an org account under a person is wrong in a way that is worse than finding nothing, and the good extractors reject them anyway. Kept inside `<article>` and smolweb-valid: one `<p>`, closed, no new elements. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
1 parent e3882eb commit bfabef4

1 file changed

Lines changed: 4 additions & 0 deletions

File tree

src/blog.ts

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -140,6 +140,10 @@ ${content}
140140
<a href="../blog">back to my blog postings</a>
141141
</nav>
142142
143+
<p>Find me: <a rel="me" href="https://defcon.social/@chovy">Mastodon</a> &middot;
144+
<a rel="me" href="https://github.com/ralyodio">GitHub</a> &middot;
145+
<a rel="me" href="mailto:anthony@profullstack.com">email</a></p>
146+
143147
</article>
144148
145149
</body>

0 commit comments

Comments
 (0)