Glossary aktualisiert

Philip (a-0) 2024-02-25 09:47:10 +00:00
parent 6871b720f0
commit 380596b7f6

@ -10,10 +10,13 @@ A group of peers which assume absolute trust among each other. A peer can demand
## Message ## Message
Data format used in communication between peers. They can contain administrative data (like resolving a peer's name), or payload data (like element updates, creations etc.). Data format used in communication between peers. They can contain administrative data (like resolving a peer's name), or payload data (like element updates, creations etc.).
## Peer ## Node
Peers are actors within the `ubisync` network. They provide a way for apps to share data to other peers, manage and search it. A peer has exactly one active I2P identity at any given time. Brigdes the gap between a peer in the `ubisync` network and apps wanting to interact with it. The node contains the peer, a means of storing data such as elements, permissions etc., and should expose an API for apps to use.
In the common use case, a peer represents one device of a user, while the family represents the user himself (as the collection of all of his devices). Typically, each device of a user runs exactly one node.
## Peer
Peers are the network perspective of a node. At any given time, a peer has exactly one active I2P identity. Peers provide the ability to communicate with other nodes to their local node, not performing any higher-level tasks such as conflict resolution etc.
## Pot ## Pot
Group of elements, every element belongs to exactly one pot. A pot is created with an app type, suggesting a way the elements may be used. Thus, the pot and its app type provides context to the loose collection of tagged elements inside it. Group of elements, every element belongs to exactly one pot. A pot is created with an app type, suggesting a way the elements may be used. Thus, the pot and its app type provides context to the loose collection of tagged elements inside it.