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

Refactor Database Model #219

Open
LNA-DEV opened this issue Aug 7, 2023 · 6 comments
Open

Refactor Database Model #219

LNA-DEV opened this issue Aug 7, 2023 · 6 comments
Assignees
Labels
enhancement New feature or request

Comments

@LNA-DEV
Copy link
Member

LNA-DEV commented Aug 7, 2023

No description provided.

@LNA-DEV LNA-DEV added the enhancement New feature or request label Aug 7, 2023
@LNA-DEV LNA-DEV added this to Fedodo Aug 7, 2023
@LNA-DEV
Copy link
Member Author

LNA-DEV commented Aug 7, 2023

Currently the database is based on an Inbox => Type model. But I think it has to be an Inbox => Actor model.

@LNA-DEV
Copy link
Member Author

LNA-DEV commented Aug 7, 2023

This issue only is about the model of Outbox and Inbox

@LNA-DEV LNA-DEV self-assigned this Aug 7, 2023
@LNA-DEV
Copy link
Member Author

LNA-DEV commented Aug 7, 2023

The Collections in the Outbox should be grouped by Actors

@LNA-DEV
Copy link
Member Author

LNA-DEV commented Aug 7, 2023

The Inbox should be treated same as the Outbox.

@LNA-DEV
Copy link
Member Author

LNA-DEV commented Aug 7, 2023

This design would make much more sense. "Save the data together which is accessed together"

@LNA-DEV
Copy link
Member Author

LNA-DEV commented Aug 8, 2023

I just thought about that topic again. New idea:

Activity Database

This 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: No status
Development

No branches or pull requests

1 participant