You are reading content from Scuttlebutt
@Dominic %1JVLpZdOdF3qx6bN0fBnaswt+prU5271K8XhmMimHPM=.sha256
Re: %IJQn5jYEX

@elavoie TODO: implement fork proofs. if you see two seemly valid messages with the same sequence, you could publish a "fork proof" that shows that feed has forked, and other peers seeing that and validating the proof would then stop replicating that feed. This feature was mainly waiting on ssb-ooo.

This will mean that if you copy someone's keys the worse you could do would be kill their identity (they'd have to start again, same as if they lost their key)... although if you never published anything you could still read their private messages.

Join Scuttlebutt now