Joining the IndieWeb

Why I made my own domain the canonical home of everything I publish, and how rel=me and h-card verified my identity on the old site.

After years of posting on other people's platforms and watching some of them quietly rot, I wanted my site to be the canonical place for everything I publish. The IndieWeb gave that a concrete shape: you own your content, it lives on your domain, and everything else is a distribution channel. This was the first step on my old Astro site: identity, through rel=me and h-card.

The core idea

Most personal publishing flows the wrong way. You write on a platform, the platform owns the URL, and if it dies or changes its terms, your content goes with it.

POSSE (Publish on your Own Site, Syndicate Elsewhere) reverses this. The canonical URL is always yours, and copies go out to other networks from there. The IndieWeb needs no particular stack or service. It is a collection of small standards that work over plain HTTP, so a static Astro site qualifies as well as a WordPress blog.

rel=me and identity

Saying "I am the same person at these URLs" means nothing if nothing checks it. rel=me declares that two URLs belong to the same person. It goes on links to profiles elsewhere:

<link rel="me" href="https://github.com/adrian-altner" />
<link rel="me" href="https://bsky.app/profile/adrian-altner.de" />
<link rel="me" href="https://www.instagram.com/adrian.altner/" />
<link rel="me" href="https://www.linkedin.com/in/adrian-altner/" />

The link only counts when the other side confirms it. On GitHub you set your website in the profile. Once https://github.com/adrian-altner links back to adrian-altner.de, the circle closes.

Bluesky is a special case. Its verification does not go through rel=me HTML but through the AT Protocol's DNS or HTTPS well-known mechanism. Using the domain as the handle (@adrian-altner.de) is the verification, and after that the rel=me link to the Bluesky profile is recognised.

h-card: who you are, for machines

rel=me establishes ownership but does not describe who you are. That is what h-card does, a Microformats2 class pattern on ordinary HTML:

<div class="h-card">
    <img class="u-photo" src="/avatar.jpg" alt="Adrian Altner" />
    <a class="u-url p-name" href="https://adrian-altner.de">Adrian Altner</a>
    <p class="p-note">
        Key Account Manager IT by day, developer and photographer by hobby.
    </p>
</div>

u-url marks the canonical URL, p-name the display name, u-photo the avatar and p-note a short bio. Any MF2 parser or IndieWeb service can read a structured identity from it, with no JSON-LD and no separate metadata file.

One catch: the avatar needs a stable, unprocessed path. Astro hashes processed images, so I kept a copy at public/avatar.jpg for a permanent URL.

Checking it

indiewebify.me follows the rel=me links, confirms the backlinks, parses the h-card and reports what it finds. All three sections came back green after the first deploy.

The next steps were making single posts machine-readable with h-entry and then receiving and sending webmentions.

Takeaways

  • The first step needs nothing installed. rel=me, h-card and plain HTTP were the whole stack.
  • Verification is mutual. A rel=me link on your site only counts if the profile links back, and each platform does that in its own way.
  • Bluesky has its own path. A domain handle through the AT Protocol closes the loop there, not rel=me HTML.

More on this

Topic
  • IndieWeb Publishing on your own domain first and connecting personal websites with open standards such as Webmention and Microformats.
Mentioned in
  • POSSE to Bluesky with the AT Protocol A Node script at the end of every deploy that posts new articles from the RSS feed to Bluesky as rich link cards, straight through the AT Protocol API.
Mentioned
  • Astro Tool for building websites from content such as Markdown. Ships plain HTML by default and only loads JavaScript where it is needed.
  • Marking Up Posts with Microformats2 h-entry h-entry, h-card, h-feed and u-syndication classes on articles, notes and photos of an Astro site, machine-readable without any visible change.
  • Receiving and Sending Webmentions Incoming webmentions through webmention.io, rendered at build time in Astro, and outgoing ones sent by webmention.app after every deploy.

Show in the graph view →