Weird — #Pleroma 's #WebFinger can return (#XML based) #XRD data (rather than just (#JSON based) #JRD data).
I think the expectation from IETF #RFC7033 is that — WebFinger returns JRD (i.e., JSON Resource Descriptor format).
...
I wonder if this causes any problems with any 3rd party client apps.
#pleroma #webfinger #xml #xrd #json #JRD #rfc7033
As far as the #Fediverse 's usage of #WebFinger is concerned —
Fediverse software (including Mastodon, Pixelfed, Calckey, Pleroma, Lemmy, etc) don't seem to use the #JRD “property” element.
But if any of them ever do — since the "type" is supposed to be a URI — I think it would be better to use something like a #tagURI or something like it (rather than an HTTP(S)-URI).
Else it may suffer from #linkRot (just ostatus·org).
#fediverse #webfinger #JRD #taguri #linkrot
Using Web Host Metadata's #XRD & #JRD to figure out where #WebFinger is seems unnecessarily complex to me.
(This is used by some #Fediverse software.)
...
/.well-known/host-meta
/.well-known/host-meta.json
...
#xrd #JRD #webfinger #fediverse #rfc6415 #rfc7033
Using Web Host Metadata's #XRD & #JRD to figure out where #WebFinger is seems unnecessarily complex to me.
(This is used by some #Fediverse software.)
...
/.well-known/host-meta
/.well-known/host-meta.json
#xrd #JRD #webfinger #fediverse