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

Support delivery to shared inboxes #27

Open
cjslep opened this issue Apr 24, 2018 · 4 comments
Open

Support delivery to shared inboxes #27

cjslep opened this issue Apr 24, 2018 · 4 comments
Labels
feature request New request for novel functionality

Comments

@cjslep
Copy link
Member

cjslep commented Apr 24, 2018

No description provided.

@cjslep cjslep added the feature request New request for novel functionality label Apr 24, 2018
@cjslep cjslep added this to the 0.2.0 milestone May 9, 2018
@cjslep cjslep modified the milestones: 0.2.0, 0.3.0 Jul 13, 2018
@cjslep cjslep removed this from the 0.3.0 milestone Aug 1, 2018
@cjslep
Copy link
Member Author

cjslep commented Feb 28, 2019

I'm going to leave this open, but I want to note that I am hesitant to add the sharedInbox optimization at this time.

@aschrijver
Copy link

Could you explain a bit more about why you are hesitant as background info? Thanks :)

@cjslep
Copy link
Member Author

cjslep commented Oct 16, 2020

Sure, it's simple:

sharedInbox is the only* ActivityPub feature that breaks the Actor model. When you look at any Activity, its addressing (to, bto, cc, bcc, audience) does not align with what bytes actually got shipped to which actors on the network when using sharedInbox. Sending to the sharedInbox isn't sending an Activity to an Actor at all.

*Inbox Forwarding does not count because the entire process still preserves the Actor model: every step of the way is still shipping bytes to the actors directly.

@aschrijver
Copy link

Makes perfect sense, thanks!

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

No branches or pull requests

2 participants