yes yes yes.

@regular this is super awesome. @matt and I have talked about this and about possible minimal paths into it. My idea of a first step was messages that know how to render themselves and the content + renderer are both in a DAT blob, an example would be an album. The next iteration in is a content/ renderer which knows how to render itself and is allowed to publish (limited) content, an example of this would be a poll or a scry!

I think I take this incremental approach because it's quite an uber-vision, there are a lot of moving parts and I like the idea of getting useable solutions on the way to the top of the mountain. The advantage is you don't need to solve all the things, nor ffigure out what are actually important to solve, because your prototypes tell you that by catching on fire! But I think you've got a systems perspective and can see a little further than I some of the requirements and pitfalls. I think what I'm saying is "I would love to see more of what you're seeing, AND if it's useful I would love to support by helping form an idea of how to do this without going way out to sea (I don't want to lose you on thise quest)". (why am I so cautious... I don't know. sigh. perhaps I retract my offer of being an apprentice star-reader and instead sign up as a deck hand or cabin boy)

Also to know : parts of this dream have been dreamed by others already. You might want to follow @paul and search brickhouse (when are searches going to be a first-class citizen in ssb? I want to share searches!)

I love the name and mutinous vibe. It invokes the right balance of aspirational abundance and biligerant defiance. Did you know that the Bay of Plenty is a place in NZ! (they produce a lot of avocados)