You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Section 7.5 Server to Server Interactions: Follow Activity says:
The Accept or Reject MAY be generated automatically, or MAY be the result of user input (possibly after some delay in which the user reviews).
However, there is no corresponding guidance anywhere in 6. Client to Server Interactions for both Accept and Reject Activities, so organizationally it is non-intuitive to have to go to section 7.5 to learn that:
Servers MAY choose to not explicitly send a Reject in response to a Follow, though implementors ought to be aware that the server sending the request could be left in an intermediate state.
And since there is no explicit guidance on the Client to Server section, a spec-compliant implementation could also not deliver Accepts as well. (Since the MUST in 6.11 Delivery seems to be violated in quite a few places).
The text was updated successfully, but these errors were encountered:
This is a useful note. I've added further documentation on the Follow, Accept, and Reject activities to the Primer to make it clearer what checks should be done, ideally, as well as what side effects the activities have.
Section 7.5 Server to Server Interactions: Follow Activity says:
However, there is no corresponding guidance anywhere in 6. Client to Server Interactions for both
Accept
andReject
Activities, so organizationally it is non-intuitive to have to go to section 7.5 to learn that:And since there is no explicit guidance on the Client to Server section, a spec-compliant implementation could also not deliver
Accepts
as well. (Since the MUST in 6.11 Delivery seems to be violated in quite a few places).The text was updated successfully, but these errors were encountered: