A few days ago, @chrisshank.com went around the Atmosphere asking apps to adopt a small community proposal: when a web page is built out of AT Protocol records, say which ones in the page's meta tags.
Since so many have already implemented it, I figured I could do the same for @skypress.blog :)
The proposal defines 4 names:
at:canonicalpoints at the records a page is made of; if they went away, the page wouldn't have much reason to exist.at:alternatepoints at records the page merely shows.at:authorandat:mepoint at the identity behind it.
So an article on SkyPress now carries this:
<meta name="at:canonical" content="at://did:plc:.../site.standard.document/3mon4axdqjs2c" />
<meta name="at:alternate" content="at://did:plc:.../site.standard.publication/3mnuandrwh22s" />
<meta name="at:alternate" content="at://did:plc:.../app.bsky.feed.post/3mon4axgu5d2r" />
<meta name="at:author" content="at://did:plc:..." />
<meta name="at:me" content="at://did:plc:..." />That's the document you wrote, the publication it belongs to, the companion Bluesky post, and you. Publication pages and profile pages carry their own, shorter version of the same thing.
None of this is new information. Like most / all of the services on the list above, SkyPress already had <link rel="site.standard.document"> tags doing a rough version of this job. The Bluesky PR swaps those out for the new meta tags, in part because a rel value nobody registered isn't really valid HTML. On my end I kept the old tags and put the meta tags next to them, so anything already reading the old ones keeps working.
I also opted not to show a at:canonical on profile pages. Your /@handle page is a list of your publications with your Bluesky profile draped over it. If that profile record disappeared, the page would still be perfectly fine, so I think that qualifies as an at:alternate and not a canonical.