@julian@activitypub.space Hi yes we send to sharedInbox when there's more than one recipient on that instance, otherwise direct to to the user's inbox.
Discussion
Loading...
@julian@activitypub.space Hi yes we send to sharedInbox when there's more than one recipient on that instance, otherwise direct to to the user's inbox.
Re: Bonfire shared inbox usage
@mayel@bonfire.cafe oh that is an interesting choice. I suppose that makes sense, I never really thought about it. NodeBB just sends to shared inbox if available.
@julian @mayel subtle difference: sharedInbox is not delivering to the individual inboxes, and it is not strictly delivering to the addressed actors either. what it *actually* means is "make the shared inbox decide who gets it, using the addressing as a *hint*". in theory, the shared inbox is supposed to distribute the activity to the appropriate inboxes internally. this, of course, leads to Problems when the shared inbox doesn't understand a specific recipient (like with private collections)
Re: Bonfire shared inbox usage
@trwnh@mastodon.social that sounds like a them problem not a my problem 😝
@julian @mayel well, that's exactly it! you never said which inboxes to deliver to, so my shared inbox has to *guess*...
https://w3id.org/fep/0499/multibox tries to avoid this by using an Add activity targeting the specific inboxes, iirc. (probably should revisit that FEP...)