Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should Endpoint Discovery documentation match Webmention spec? #112

Open
jgarber623 opened this issue Jul 27, 2018 · 1 comment
Open

Should Endpoint Discovery documentation match Webmention spec? #112

jgarber623 opened this issue Jul 27, 2018 · 1 comment

Comments

@jgarber623
Copy link
Contributor

Hello!

In a conversation in IndieWeb IRC (in the dev channel) regarding the differences between the Webmention spec's endpoint discovery algorithm and the Micropub spec's endpoint discovery algorithm, @sknebel noted:

in practice, those are identical, the micropub one is just documented a lot less detailed

I tend to agree that that should be the case. I don't have the historical context for why the two specs might differ as written (vs. how implementors are implementing…) so I can't comment on that.

But… given the generalized nature of "endpoint discovery" and the common means by which website's supply this information (e.g. a <link> element, a Link HTTP header, an <a> element) it may be a good idea to bring the various specs into alignment.

So, should this section of the Micropub spec be updated to match Webmention's endpoint discovery documentation?

@jalcine
Copy link

jalcine commented Jun 6, 2019

I think it should! I currently do this with my personal site via Koype. This is largely in the event that a consuming client wanted to opt for HEAD requests before making a full-on GET (expensive for the server; cheap for clients).

(Originally published at: https://v2.jacky.wtf/post/ffb77ba1-5397-4f60-bb0f-65f302ed10c2)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants