-
Notifications
You must be signed in to change notification settings - Fork 0
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
Refactor Database Model #219
Comments
Currently the database is based on an Inbox => Type model. But I think it has to be an Inbox => Actor model. |
This issue only is about the model of Outbox and Inbox |
The Collections in the Outbox should be grouped by Actors |
The Inbox should be treated same as the Outbox. |
This design would make much more sense. "Save the data together which is accessed together" |
I just thought about that topic again. New idea: Activity DatabaseThis database will contain every Activity sent by an actor. So every actor gets a own collection in which every activity this actor sends will be stored. This should be regardless of the home server of the actor. |
No description provided.
The text was updated successfully, but these errors were encountered: