I've wanted to write a longer blog post about this, but after a few years of working on SSB I appreciate you highlighting these pain points. I think everyone in

I've wanted to write a longer blog post about this, but after a few years of working on SSB I appreciate you highlighting these pain points. I think everyone in the SSB maintainer community feels the same way. My hot take: Scuttlebutt should be something that you can implement yourself in an afternoon. I've done this a few times, using Python, Node.js, and Deno, but I've only implemented the message type. (Not Multiserver, MuxRPC, Secret-Handshake, Box-Strean, Private-Box, or any of the other protocols that are associated with SSB.) > It feels like Git. You got it. You could express an SSB chain with Git and a pre-commit hook (to verify messages), but using Git as your database is even harder than learning the toy database that SSB uses. Various links: - My SSB data expressed as a Git repository (outdated): https://github.com/christianbundy/ssb-git-data https://github.com/christianbundy/ssb-git-data - My speedrun SSB implementation with SQLite, using HTTP for replication: https://github.com/christianbundy/http-ssb https://github.com/christianbundy/http-ssb