home.social

#rfc7033 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #rfc7033, aggregated by home.social.

fetched live
  1. teledyn 𓂀 @[email protected] ·

    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? 🤨

    #webfinger #wordpress #rfc7033
  2. @reiver ⊼ (Charles) :batman: @[email protected] ·

    @J12t

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

    rfc-editor.org/rfc/rfc6415.htm

    #WebFinger 's IETF #RFC7033 mentions that here:

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

    #hostmeta #webfinger #rfc6415 #rfc7033
  3. @reiver ⊼ (Charles) :batman: @[email protected] ·

    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
  4. @reiver ⊼ (Charles) :batman: @[email protected] ·

    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

    #xrd #jrd #webfinger #fediverse #rfc6415 #rfc7033