Backoff strategy for discovery

[rhiaro]

Similar to w3c/webmention#48, how many times should a Sender/Consumer that wants to do discovery several times on one resource, or multiple target resources on the same domain, try to find the inbox endpoint before it gives up? To avoid knocking over a server, or being blocked for too many GET requests?

[rhiaro]

Update: webmention is resolving this by adding something or replacing the User-Agent value (if present) but I think this is not possible or very complicated for JS implementations, so not a good recommendation for LDN

[akuckartz]

I suppose that guidelines regarding such http-questions exist somewhere.

[csarven]

Added a non-normative sub-section "Retry Discovery" under Considerations: da56c9a

[rhiaro]

F2F resolution was to add note to SWP (or external Note) about not accidentally beating servers up with discovery. Unless @BigBlueHat finds an existing note about it first.

w3c-social/social-web-protocols#38

[rhiaro]

Decision: Put a specific link in Discovery section linking to section in SWP.

[aaronpk]

What does "courteous" mean? Also this fragment ID referenced in 2bf7c0b doesn't seem to exist https://www.w3.org/TR/social-web-protocols/#targeting-and-discovery

[BigBlueHat]

Perhaps recommending something quantifiable like Exponential Backoff would be best. There are lots of libraries for most common programming languages that do that--even for HTTP APIs.

[rhiaro]

Sorry about the broken SWP fragment, it's pre-empting a new WD: http://w3c-social.github.io/social-web-protocols/#targeting-and-discovery