... | ... | @@ -27,18 +27,20 @@ Pleroma only had a traditional concept of `users` though, so changes we need to |
|
|
* `primary_user_id` indicates the `user` linked to that `Actor`, or who originally created that group
|
|
|
* `actor_type` can include `Person`, `Group`, `Community`, `Curation`, `Organisation`, etc
|
|
|
* `actor_openness` is optional and could include `invite-only`, `moderated`, `open`, etc
|
|
|
* `ap_id` indicates the `actor` URL
|
|
|
* `actor_uri` (renamed from `ap_id`) indicates the `actor` URI
|
|
|
* `actor_relationships` (to store memberships and permissions of groups)
|
|
|
* `subject_actor_id` could represent an Person agent like Alice
|
|
|
* `object_actor_id` could represent a `Group` agent like 'Geographers of the world'
|
|
|
* `relationship_type` could be `admin`, `moderator`, `contributor`, `participant`, `viewer`, etc
|
|
|
* `subject_actor_id` could refer to a Person agent like Alice
|
|
|
* `target_actor_id` could refer to a `Group` agent like 'Geographers of the world'
|
|
|
* `relationship_type` could be `following`, `admin`, `moderator`, `contributor`, `participant`, `viewer`, etc
|
|
|
* `relationship_confirmed` indicates whether the object has confirmed the relationship requested by the subject (for example a moderator has approved Alice's request to join the group)
|
|
|
|
|
|
Here's an updated DB structure:
|
|
|
|
|
|
![tables_SQLEditor_v2](uploads/fd7f40b37c4a2bb34da8533d3f53b01d/tables_SQLEditor_v2.png)
|
|
|
![tables_SQLEditor_v3](uploads/b6695ca622b9990ec8cf6da3f867ea7b/tables_SQLEditor_v3.png)
|
|
|
|
|
|
## To research
|
|
|
|
|
|
|
|
|
## Options to research
|
|
|
* http://leveldb.org/
|
|
|
* https://dgraph.io
|
|
|
|
... | ... | |