> However, the remote server might not know how to deliver the activity to private recipients, or recipients within a collection. The multibox endpoint removes this knowledge requirement from the receiving server and instead makes the sending server responsible for marking inboxes to explicitly deliver to.

@silverpill I think needs clarification, it's not obvious to me how another end-point that you need to know about and needs to be discovered makes things better than plain old sharedInbox. The large combination matrix that
@rimu mentions, is not really so apparent for activities that aren't addressed to the public collection IMHO.

@smallcircles