{"action":"created","issue":{"url":"https://api.github.com/repos/w3c-social/webmention/issues/13","labels_url":"https://api.github.com/repos/w3c-social/webmention/issues/13/labels{/name}","comments_url":"https://api.github.com/repos/w3c-social/webmention/issues/13/comments","events_url":"https://api.github.com/repos/w3c-social/webmention/issues/13/events","html_url":"https://github.com/w3c-social/webmention/issues/13","id":119281676,"number":13,"title":"Why not allow multiple webmention endpoints?","user":{"login":"kevinmarks","id":99008,"avatar_url":"https://avatars.githubusercontent.com/u/99008?v=3","gravatar_id":"","url":"https://api.github.com/users/kevinmarks","html_url":"https://github.com/kevinmarks","followers_url":"https://api.github.com/users/kevinmarks/followers","following_url":"https://api.github.com/users/kevinmarks/following{/other_user}","gists_url":"https://api.github.com/users/kevinmarks/gists{/gist_id}","starred_url":"https://api.github.com/users/kevinmarks/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kevinmarks/subscriptions","organizations_url":"https://api.github.com/users/kevinmarks/orgs","repos_url":"https://api.github.com/users/kevinmarks/repos","events_url":"https://api.github.com/users/kevinmarks/events{/privacy}","received_events_url":"https://api.github.com/users/kevinmarks/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-11-28T09:15:37Z","updated_at":"2015-11-28T18:07:28Z","closed_at":null,"body":"Currently the spec says:\r\n\r\n>The webmention endpoint is advertised in the HTTP Link header or a `<link>` or `<a>` element with `rel=\"webmention\"` . If more than one of these is present, the HTTP Link header takes precedence, followed by the `<link>` element, and finally the `<a>` element. Clients MUST support all three options and fall back in this order.\r\n\r\nHowever it does not address what should be done if multiple endpoints are indicated for a page using one of these techniques.\r\n\r\nI'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.\r\n\r\nIn addition, if you are migrating from one webmention service to another, being able to [ping both](http://indiewebcamp.com/irc/2015-11-28/line/1448701528335) in parallel is best practice to ensure consistency. \r\n\r\n"},"comment":{"url":"https://api.github.com/repos/w3c-social/webmention/issues/comments/160325121","html_url":"https://github.com/w3c-social/webmention/issues/13#issuecomment-160325121","issue_url":"https://api.github.com/repos/w3c-social/webmention/issues/13","id":160325121,"user":{"login":"dissolve","id":2546145,"avatar_url":"https://avatars.githubusercontent.com/u/2546145?v=3","gravatar_id":"","url":"https://api.github.com/users/dissolve","html_url":"https://github.com/dissolve","followers_url":"https://api.github.com/users/dissolve/followers","following_url":"https://api.github.com/users/dissolve/following{/other_user}","gists_url":"https://api.github.com/users/dissolve/gists{/gist_id}","starred_url":"https://api.github.com/users/dissolve/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dissolve/subscriptions","organizations_url":"https://api.github.com/users/dissolve/orgs","repos_url":"https://api.github.com/users/dissolve/repos","events_url":"https://api.github.com/users/dissolve/events{/privacy}","received_events_url":"https://api.github.com/users/dissolve/received_events","type":"User","site_admin":false},"created_at":"2015-11-28T18:07:28Z","updated_at":"2015-11-28T18:07:28Z","body":"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."}}