I could put a lot of words around why's and but's on this topic but will try to keep it brief: Thank you for rebuilding this stuff!

I guess the gist is, go-ssb kept growing even when it was time to rethink and rebuild the layers... especially when I was working on it all on my own. It became my little playground to try implementing more and more parts of the protocol and it work for me because I knew where the skeletons are... I'm really glad to see that some of the building blocks remain useful, definitely appreciated and made my day.

What I'm not entirely clear about is how you imaging the storage system. I poked a little into the code and saw etcd's bolt fork. Is this just for the KV stuff that badger was used for or is it for all of the storage stuff? Last time I heard it sounded like you want to abstract the storage such that sqlite would still be used in planetary.

Looking at the new query package again, I notice it only has the operators type:xzy and author:@foo which can be combined with boolean operators to create more complex queries. So for root: %foo... you would be out of luck but it would a simple addition because that index already exists! Which I totally forgot when sending cblgh some context and ideas...

What you can do today is uses tangles.thread "%foo..." to get all the relevant messages, sorted by the previous lonks. It's supplied by this plugin. It could use more fleshed out tests and docs, though.