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

Inbox Forwarding Clarification #304

Open
cjslep opened this issue May 3, 2018 · 0 comments
Open

Inbox Forwarding Clarification #304

cjslep opened this issue May 3, 2018 · 0 comments

Comments

@cjslep
Copy link

cjslep commented May 3, 2018

The spec reads:

To do this, the server MUST target and deliver to the values of to, cc, and/or audience if and only if all of the following are true

The values of to, cc, and/or audience contain a Collection owned by the server.

The server MUST only target the values of to, cc, and/or audience on the original object being forwarded

The way the above reads to me is that if any of the to/cc/audience are a Collection owned by the server, then all of the to/cc/audience values on the original object are to be delivered to.

Some suggestions:

To do this, the server MUST examine each value of to, cc, and/or audience and deliver the Activity to it if and only if such a value satisfies all of the following criteria

The to, cc, and/or audience value is a Collection owned by the server.

The server MUST only examine the values of to, cc, and/or audience on the original object being forwarded

For example, given example.com receiving:

{
  type: "Create",
  to: [
    "http://example.com/addison",
    "http://foo.bar/brook"
  ],
  cc: "http://example.com/addison/followers"
}

I think the intention is for example.com to forward the activity to only http://example.com/addison/followers, though the language of the spec makes it hard to discern this. Thankfully, the example in the spec does help highlight the intentions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant