Node families #5

Open
opened 2024-01-24 00:06:26 +00:00 by philip · 0 comments
Owner

Nodes can belong to no or one family of nodes, which trust each other and exchange information without explicit shares or such. A node family can e.g. represent the nodes on all devices of some user.

  • Add necessary messages for family creation and for removing nodes from a family
  • Database: store family nodes (e.g. in peers table)
  • Periodically sync directories of all available pots with other family nodes
  • Make sure the trust assumed until now for testing purposes is only assumed for families from now on, e.g. in blindly accepting elements etc.
Nodes can belong to no or one family of nodes, which trust each other and exchange information without explicit shares or such. A node family can e.g. represent the nodes on all devices of some user. - [ ] Add necessary messages for family creation and for removing nodes from a family - [x] Database: store family nodes (e.g. in peers table) - [ ] Periodically sync directories of all available pots with other family nodes - [ ] Make sure the trust assumed until now for testing purposes is only assumed for families from now on, e.g. in blindly accepting elements etc.
philip added this to the v1 milestone 2024-01-24 00:06:26 +00:00
philip added the
Kind/Security
Kind/Feature
labels 2024-01-24 00:06:26 +00:00
philip added the
crate/ubisync
crate/ubisync-lib
crate/ubisync-sdk
labels 2024-02-11 14:23:44 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: philip/ubisync#5
No description provided.