Have started off today by digging into the awesome resources created by @RangerMauve on github . Can't remember how I got started on this train of things… I was updating my website nichoth.com. It pulls posts/photos from my ssb client and writes them to an html file using hyperstream. I got the tags plugin to work also. So photos can be indexed based on tags now in the website.
Need to fix things on eventual-gram… when you first run the app it doesn't know your name or avatar.
The difficult thing for all p2p programming seems to be local storage at this point in time. There is indexedDB in the browser, but that is more like a local cache because there is no way to know how much space you will have or when things will be deleted. This got me thinking about out of order messages/partial replication in ssb. It seems that is the only thing missing to let it work in a browser. However I can't say that I understand the terminology being used in the existing writing about it. For example, here, I don't get the use of the term 'merkle tree'. My understanding is that ssb currently does use a merkle tree, which is just the git-like structure of using posts that contain a signed hash of the previous hash (blockchain-ish).
It seems the best option is p2p + a 'pinning' server to make sure things are available (which is like a pub server in ssb).
- https://github.com/ssbc/ssb-server/issues/124 -- partial replication issue
- https://github.com/ssbc/ssb-db/issues/27 -- 'Merkle Tree Logs' issue
- https://viewer.scuttlebot.io/%25L9m5nHRqpXM4Zkha1ENTk5wNOXQMduve8Hc9%2BF0RLZI%3D.sha256 -- ssb thread about enabling partially subscribable feeds