Conversation

Notices

1. Embed this notice
   Evan Prodromou (evan@cosocial.ca)'s status on Monday, 22-Apr-2024 04:35:31 JST Evan Prodromou

   @julian @nightpool agreed. That's positive behaviour.

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Wednesday, 24-Apr-2024 01:30:38 JST Evan Prodromou

     in reply to

     • blaine

     @blaine @julian @nightpool

     So, for finding the AP equivalent of an URL that I think is a Web page, I'd take these steps:

     - Link header: HEAD and look for the Link: header (easy, fast)
     - Webfinger: Webfinger the URL (a little more complicated)
     - Content negotiation: GET with Accept header set to AS2 type
     - Parsing: GET and look for Link: header or <link> element

     For finding the HTML page for an AP object:

     - Link header: HEAD and look for Link:
     - AS2: GET and look for `url` at top level

   • Embed this notice
     blaine (blaine@mastodon.social)'s status on Wednesday, 24-Apr-2024 01:30:39 JST blaine

     in reply to

     @evan @julian @nightpool for what it's worth, webfinger should be (re: is) able to do this, even if the implementations in the wild don't. The intent at the time was for webfinger to be the "DNS records" for "social addresses", and the main reasons we didn't just use DNS was because (1) DNS doesn't support anything but bare domain names, (2) management of DNS records at scale is hard, and (3) it wasn't possible to query DNS via the web.

   • Embed this notice
     blaine (blaine@mastodon.social)'s status on Wednesday, 24-Apr-2024 01:30:39 JST blaine

     in reply to

     @evan @julian @nightpool lots of folks advocated to support any URI scheme in a webfinger lookup, and that's why we have the "acct" scheme at all - so that email-style addresses could be used alongside http etc URIs!

     The <Link> approach definitely works, but feels a bit reinventing-webfinger/creating more complexity in lookups (on the client side).

     Hope the context is helpful! 😊

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Wednesday, 24-Apr-2024 01:45:59 JST Evan Prodromou

     in reply to

     • blaine

     @blaine @julian @nightpool

     For finding the HTML page for an AP object:

     - Link header: HEAD and look for Link:
     - Content negotiation: HEAD with Accept: set to text/html
     - AS2: GET and look for `url` at top level

   • Embed this notice
     blaine (blaine@mastodon.social)'s status on Wednesday, 24-Apr-2024 02:50:24 JST blaine

     in reply to

     @evan @julian @nightpool in the Postel sense, though, it's too bad that a client implementor needs to maintain (at least) four discovery pathways, and may require four separate requests to validate the information. Similarly, an ap host doesn't know which spots a client will check, so needs to implement all four. I'm well out of the standards game, but I'd very much advocate for "pick one and stick with it" 😊

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Wednesday, 24-Apr-2024 02:50:24 JST Evan Prodromou

     in reply to

     • blaine

     @blaine @julian @nightpool we need you back in the standards game