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
Why not allow multiple webmention endpoints? #13
Comments
That seems like a useful thing to concretize in the spec. |
I think it makes a lot of sense to not allow multiple endpoints. Its trivially easy to set up an endpoint that just repeats the message to any number of endpoints you need and it takes the requirement off of webmention senders of possibly sending numerous webmentions. If someone starts to go a bit crazy and has 10 endpoints, we require the WM sender to send 10 POSTs? If any one implementation of a sender doesn't send to all you could miss mentions quite easily. |
I don't care much either way, but agree this should be clarified in the spec. I lean slightly toward agreeing with @dissolve. One related concept is the idea of adding a type parameter to the rel=webmention (headers and elements) to provide con-neg without an additional round-trip. In this case, the client would look through the links for one which had a type it understood/preferred. |
Allow mutiple |
Clarify only the first endpoint should be used: https://indiewebcamp.com/wiki/index.php?title=Webmention&diff=23674&oldid=23673 I also added an FAQ based on what we discussed at the F2F meeting: https://indiewebcamp.com/Webmention-faq#What_if_multiple_webmention_endpoints_are_discovered Does this cover it for everyone here? |
Closing this as complete based on today's call |
Marking as commenter satisfied based on his +1 in the minutes https://www.w3.org/wiki/Socialwg/2015-12-08-minutes |
Currently the spec says:
However it does not address what should be done if multiple endpoints are indicated for a page using one of these techniques.
I'd suggest that in this case, sending a webmention to each one found makes sense. As webmention does not define what endpoints should do, it is clear that there could be different webmention triggered services - one that creates useful comment threading, and one that caches linked-from pages, for example.
In addition, if you are migrating from one webmention service to another, being able to ping both in parallel is best practice to ensure consistency.
The text was updated successfully, but these errors were encountered: