I replied to the following: ↷
#54 DNS SRV entries for endpoint discovery
The discovery chapter suggests that The client first performs discovery on the user's profile URL to find the Microsub endpoint and authorization endpoint. Then endpoints should be discovered from the profile page.
Some feed aggregators (I am thinking of nextcloud-news or newspipe) would benefit from implementing microsub, but implementing a profile page just for the sake of the discoverability might feel out-of-scope (although nextcloud itself might be a good candidate to do this).
Other protocols define DNS SRV entries that can be used for discovery. For instance:
- RFC6186 for SMTP, POP and IMAP,
- RFC6764 for CalDAV and CardDAV,
- The matrix protocol defines its SRV entries.
I suggest that the microsub-spec defines DNS SRV entries as an alternative endpoint discovery method, so clients might discover the microsub endpoints just by the domain.
What do you think?
azmeuk
•
posted
•
archived copy
•
currentThe first part! Also, it's important to note that Microsub implies a use of IndieAuth (via https://indieweb.org/Microsub-spec#Authentication_and_Authorization), which sets the idea of a profile URL being present as a normal behavior. The DNS lookup / peeking would be a bit out of the range of this.
Posted with Quill at in Everything
Shared to GitHub
Engagement is powered by Webmentions — a premier standard of the Web to let other sites know you've mentioned them. Learn how to reply from your own site. or from a supported silo Aaron has an interactive post about this. If you've mentioned this URL via another one, use the form below to submit it.
If you don't currently own your replies, then you can click below to do so.
I currently aim to own my comments and plan to eventually show those I've received once I finish Lighthouse.