Address feedback to p2p data sync

[oskarth]

Andrea

ok, looks good a couple of things, first about causal consistency. If you are talking about causal consistency it's also important to specify what is considered causally related, for example bramble guarantees causal consistency only for threads in a group chat (all messages are causally ordered as it uses lamport timestamps, but that's different), not for one-to-one any other message etc, which is a fairly weak definition (A distributed database might define causally related any write to the whole db, that would be probably the most accepted definition)
dimension break down I would add another thing, since you are touching on upgradability
I think there is useful to know if it's an online-to-online (synchronous) protocol (i.e bramble) or asynchronous (scuttlebut probably)
...
might fit under guarantees "Requires receiver to be online"
active vs passive propagation mention

Adam

• https://notes.status.im/J-huqkXaSB2daQVBKuXV_Q?view (adam
• Clearer requirements for data sync

Also waiting for some more