ssb-db

Thanks! I would like to know if there are any projects working on this. I found this thread discussing how it could be done over SSB https://github.com/ssbc/ssb-db/issues/202

This was true until about 14 hours ago. :) https://github.com/ssbc/secure-scuttlebutt/pull/220 You can now generate an unbox key for a private message send it to a non-recipient for them to be able to access the message, which is really cool. No private key sharing necessary!

I'm not a user, but I have been watching it (and its related projects on github). I believe Patchwork[0] is the social network you joined, and it is based on scuttlebutt[1]. It seems like very early times for most people even considering the downsides of centralized 'social media,' and it will take time and hand-holding to demonstrate the alternative possibilities. A great client app that could unify the user experience, but offer power-user features could go a long way. Most people that I know (older) are not overtly interested in participating in any public social network (i.e. Twitter). I wonder if one could build a more closed, private, white-list-default (triple opt-in!) type of social network on top of SSB with the right client software? [0] "A decentralized messaging and sharing app built on top of Secure Scuttlebutt (SSB)." https:

It's written in nodejs, here is the repo: https://github.com/ssbc/secure-scuttlebutt

Your concern about APIs in distributed systems seems to neglect the fact that cryptography can be used to ensure that only the right people have access to the data. Although I do agree on the fake news point you make. Edit: It seems that scuttlebutt does support optional end-to-end encryption: https://github.com/ssbc/secure-scuttlebutt#security-properti...

Blockchain apps aren't going to happen, just how BitTorrent apps never happened. There's a bunch of reasons, but most of them come down to the fact that decentralization isn't really a boon. Consider a new social network I want to build. Making a simple prototype and hosting it on AWS is easy. Getting people to use it is hard. Getting people to use it and make them self-host some kind of "node" in this decentralized universe -- that's exponentially harder. Diaspora clearly showed that no one wants to set up and host their own nodes. And then you have to solve all kinds of really hard problems: double spending, consensus, 51%+ attacks, and so on. Some of these problems are simply unsolvable and we have to compromise. SSBT, for example, has no consensus, so everything is subjective[1] (which makes it almost impossible to do anything useful

Some of the node hacker community's work on scuttlebutt, hyperlog etc also seems highly relevant, as it's all based on merkle DAGs. https://github.com/ssbc/secure-scuttlebutt https://github.com/mafintosh/hyperlog These are all super modular so fishing around in their dependency graphs should lead you to a whole bunch of really interesting projects :)

Maybe something like this? https://github.com/ssbc https://github.com/ssbc/secure-scuttlebutt https://github.com/ssbc/scuttlebot

people interested in this should check out secure scuttlebutt [1]. it's a decentralized data network built around logs (think kappa architecture [2]) with ecc keypair identities, proof of authorship, and content-addressed linking 1. https://github.com/ssbc/secure-scuttlebutt 2. http://www.kappa-architecture.com/

Can you prove authorship with CRDTs? scuttlebutt[0] moved from a CRDT implementation to a log based structure of signed messages[1]. [0]: https://github.com/dominictarr/scuttlebutt [1]: https://github.com/ssbc/secure-scuttlebutt