Fediverse admin PSA 

Attention to

We are considering dropping support for host-meta and XRD support (inherited from GNU Social/OStatus) in next version, as the webfinger spec is enough and simpler.

As far as we know, no fediverse implementation relies solely on host-meta or XRD, so that wouldn't be a big change.

That being said, some deployments do (partly because of a guide I wrote ages ago, in OStatus times) depend on host-meta. That could be the case, for instance, if you installed Mastodon so that it is on social.domain.org but serving @foo@domain.org. In this case, please check that https://domain.org/.well-known/webfinger redirects to, or proxies, https://social.domain.org/.well-known/webfinger.

With nginx, this could be done like this:

location /.well-known/webfinger {
return 301 https://social.example.org$request_uri;


Fediverse admin PSA 

In the end, we are not going to drop support for host-meta but we are still making a few changes that may affect some instances:
1. drop support for XRD on the LLRD endpoint: in practice this doesn't seem to be an issue, but who knows
2. only fall-back to host-meta if the webfinger query raises a 404, and not if it has any other status. So if you don't have a working redirection, check that you're not throwing a 401, 403, a 500 or anything else there

I'll try finding affected instances and contacting them, but please have a look if you're running an unusual config

Sign in to participate in the conversation
Mastodon (instance perso)

This is a small personal instance running on a couple small ARM servers at home.