> Content cannot be easily edited or deleted, but the append-only log ensures that the network converges towards the same state despite partitions. I don't thi

> Content cannot be easily edited or deleted, but the append-only log ensures that the network converges towards the same state despite partitions. I don't think that's right. First, there's no single network, so I don't understand what “converging” means here. Each person has a different subset of all the scuttlebutt messages that exist. If a client discovers conflicting messages claiming to be Alice's message number 21, the client ignores both messages and all subsequent messages in that feed; the feed is “forked” — nothing converges. The purpose of the append-only log is as the paper says later: > Messages cannot be faked, omitted, or re-ordered, due to the signed append-only log nature of the feed. --- > An ignore will simply not show that data to the user's node, although their node will continue to pass their data through the network. Which client implements ignores like this? I thought that for most clients, ignore means “I won't replicate this feed, but I also won't publish a message announcing that I'm no longer replicating this feed”. The same as blocking, but without announcing it. --- > For example, a client could store data from 2 hops away, but replicate data from 3 hops away No, you can't replicate data you haven't stored! You could store and replicate data from 3 hops away but only display data from 2 hops away. --- They're a little confused, but they've got the spirit!