Webfinger provides a means for doing simple discovery of an event channel identifier (ECI) given a simple, better known account.


In last week's post on subscriptions in personal clouds, I talk about the possibility of using Webfinger for event channel discovery. The goal is to automatically retrieve a person's well-known ECI from some other identifier that they give you, hopefully one that's easier to remember and type in that a URL with a big long GUID in the middle.

This morning I decided I'd try to figure out exactly how Webfinger could work for this purpose. Turns out it's not very hard thanks to Evan Hammar's article on implementing Webfinger.

Webfinger relies on a new URI scheme, acct:, and the idea that a host can return an XRD document describing various meta-data resources about the person identified in the URI.

For example, for, we'd look in

for a resource with the name lrdd:

<?xml version='1.0' encoding='UTF-8'?>
<XRD xmlns=''
    <Link rel='lrdd'
        <Title>Resource Descriptor</Title>

The lrdd resource says how to find information about a person via a service. In this case, it's the describe service running on the same host, The resource is a template that the URI is plugged into.

Doing so, we get the following URL:

Performing an HTTP GET on that URL returns the XRD document for :

<XRD xmlns="">
  <Link rel=""

This file identifies the well-known ECI using a URI at Using a simple identifier,, we were able to retrieve a well-known ECI for a personal cloud. There would likely also be other information in my Webfinger, like a link to my HCard, etc.

This is pretty easy and only took a little while to get set up. Of course if ECIs were in wide-spread use, Google and other "account" providers could easily allow people a place to store their well-known ECI and return it via Webfinger. This isn't the only way you could do it, of course. For example, the ECI could be in an NFC or QR code on a business card.

Please leave comments using the sidebar.

Last modified: Wed Feb 12 18:25:03 2020.