SSB's root is just "hash chain + signatures", and is relatively trivial to implement. Most of the actual protocol is flawed in several ways, and there's tough

SSB's root is just "hash chain + signatures", and is relatively trivial to implement. Most of the actual protocol is flawed in several ways, and there's tough issues they are still trying to solve. I'd say something based off of IPFS for bulk storage (SSB suffers from bloat, and there's multiple proposals to move actual data off the append only log and into "blobs", which are already WAY better implemented in IPFS, IMHO), with some form of "here's the bits that make up my profile" thing, possibly similar to SSB, but with a cleaner implementation. A few things that should be high priority, IMHO: - Allow for profile "compaction"/data removal (SSB says you should never delete anything, which is frankly untenable, IMO) - Allow for multiple devices/apps to manipulate your profile concurrently (Complex, but SSB has been criticized multiple times for vigorously arguing against this capability) - Use a data protocol that is well formed and structured (SSB uses "node.js formatted" json serialization, and then verifies signature after deserializing and reserializing, meaning you must match node.js's serialization perfectly to interact with the rest of the ecosystem)