Ryan Barrett

[The WebFinger spec says](https://tools.ietf.org/html/rfc7033#section-4): > The WebFinger resource returns a JSON Resource Descriptor (JRD) as the resource representation to convey information about an entity on the Internet. I did notice...

Thanks! Yup, that's XML-based XRD. I can try supporting that and see if it works then.

OK, Bridgy Fed's WebFinger now supports XRD. If you fetch it with `Accept: application/xrd' or 'application/xml', it now returns similar XRD to Pleroma's. Feel free to retry. Thanks again for...

Thanks! I should really set up my own local Pleroma instance to do this testing. 😆 That new JSON is `.well-known/host-meta`, it needs to be XRD too. I'll do that.

OK, `/.well-known/host-meta` now defaults to XRD, [as the spec says it's supposed to.](https://tools.ietf.org/html/rfc6415#section-3) Ready to retry.

Ugh, thanks. We're back to serving JSON (JRD), and they're trying to parse it as XML (XRD), and failing. I finally got a look at the HTTP request headers Pleroma...

OK! Done, we now handle their `Accept` header and return XRD for both host-meta and webfinger queries.

Very possible! I tried re-sending with an actor just now and got an opaque 400 with body `"error"`: ```sh $ curl -v -H 'Content-Type: application/activity+json' https://social.nipponalba.scot/users/jk/inbox -d '{"@context": "https://www.w3.org/ns/activitystreams", "id":...

Ah, yes, I didn't send an HTTP sig with these since they were manual, and you said you'd disabled sig checking. If it looks like that's the blocker, I can...

@mark4409 thanks for asking! I haven't looked into it much more myself, but if you're familiar with Pleroma, feel free to try it out against a recent Pleroma version, see...