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

Client-To-Server Interactions: Accept/Reject #296

Closed
cjslep opened this issue Feb 15, 2018 · 2 comments
Closed

Client-To-Server Interactions: Accept/Reject #296

cjslep opened this issue Feb 15, 2018 · 2 comments
Labels
pending-closure-in-7-days This issue will be closed in 7 days after review

Comments

@cjslep
Copy link

cjslep commented Feb 15, 2018

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).

@evanp
Copy link
Collaborator

evanp commented Jun 14, 2023

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.

https://www.w3.org/wiki/ActivityPub/Primer/Follow_activity
https://www.w3.org/wiki/ActivityPub/Primer/Accept_activity
https://www.w3.org/wiki/ActivityPub/Primer/Reject_activity

Given this additional documentation, I'm going to set this issue to pending.

@evanp evanp added the pending-closure-in-7-days This issue will be closed in 7 days after review label Jun 14, 2023
@evanp
Copy link
Collaborator

evanp commented Jul 12, 2023

This has been pending for 1 month. I'm going to close this ticket.

@evanp evanp closed this as completed Jul 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending-closure-in-7-days This issue will be closed in 7 days after review
Projects
None yet
Development

No branches or pull requests

3 participants