Support enhanced links #32

Closed

stevedylan.dev 5mo ago

Closed opened by

stevedylan.dev 5mo ago

See https://github.com/bluesky-social/atproto/discussions/4978

Should backfill existing pages with the publication URI for efficiency with Bsky.

heaths.dev 5mo ago

The publication LINK could be added to inject for people who want to use it for static pages, but I think we'll also need to document it on the web site for how to add it if you're also emitting the LINK for the document e.g., for Jekyll I did this: https://github.com/heaths/heaths.github.io/commit/c33c844ae8d35994f73ce2fc778844866bcb7b34

  {%- if page.atUri %}
  <link rel="site.standard.document" href="{{ page.atUri }}" />
  {%- endif %}
  <link
    rel="site.standard.publication"
    href="at://did:plc:tg3tb5wukiml4xmxml6qm637/site.standard.publication/3meddhkrg5z2p"
  />

heaths.dev 5mo ago

We can use https://standard.site/docs/verification/#discovery-hint to link to official docs for more information instead of the current discussion. Seems it's ratified.

stevedylan.dev 5mo ago

Interesting! Yeah this seems pretty doable since the publication is already part of the config. I'll probably keep the old publication verification as well just to be safe.

heaths.dev 5mo ago

The old verification is actually necessary anyway. the link <link> is there as a perf optimization. If there, aggregators like what Bluesky is working on - don't need to do a separate fetch.

As the official standard.site docs state of this <link>:

This is a hint only. Do not rely on it for verification, and always confirm via the .well-known endpoint.

heaths.dev 5mo ago

Merged #64.