#rfc7033 — Public Fediverse posts

@sabrinkmann
#monopolies like the one you mentioned tend to zuck up everything while the #fedi, as I understand it, prefers to #federate and link instead. So, can't an actor provide a clickable, say matrix, handle? Has it to be mandatory? Has it to be a certain protocol? #AP? Or can there be #choice?

P.S.: auto-discovery via #webfinger / #RFC7033?

This #webfinger thing is a further puzzle. #wordpress adheres to #RFC7033 but that spec says nothing about acct beginning with @ they only use user@host examples! So is this important if a node only accepts without? Or is there a JDR trick I should know? 🤨

@J12t

"template" is defined in IETF #RFC6415 (i.e., Web Host Metadata / #hostMeta ).

https://www.rfc-editor.org/rfc/rfc6415.html

#WebFinger 's IETF #RFC7033 mentions that here:

"The JSON Resource Descriptor (JRD), originally introduced in RFC 6415"

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.

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

...

#RFC6415 #RFC7033