I love that you’re finally sharing technical documentation of your Trust Assembly ideas! 😍
Your prose in earlier posts helped to catch my interest but it’s really the technical details that enable others to see whether your ideas are pie-in-the-sky dreams or actually something worth investing time into understanding, sharing and contributing to. :)
Just speaking anecdotally: There are multiple technically-minded friends with an interest in improving societal discourse that I’ve found it difficult to share your longer prose about the Trust Assembly with. The details there are so vague that it’s hard at a glance to see whether your ideas could actually work when implemented or if they’re just whishful thinking with deal-breaking flaws in it. Being able to refer them to a technical write-up does so much to communicate “this is trust-worthy bc. you can verify for yourself if the ideas make sense”.
If you worry that the technical descriptions are too il-fitting on your blog, why not create a website that hosts all the technical information for those interested? Then you could refer to it repeatedly on this blog where you can keep the focus on communication the Trust Assembly idea to a wider audience via story-telling and big-picture ideas.
I think with my hands. I think that’s why I’m a better writer than speaker. One thing I’ve discovered in my life is that I’m weirdly good at putting a whole process together immediately in my head and knowing with high confidence if it will work or not, and less good at explaining it to everyone else in detail. Only reason I feel that isn’t delusion is because if I can manipulate physical things with my hands it becomes immediately obvious I have a model in my head I’m working from. I’m trying to bridge that gap.
I love that you’re finally sharing technical documentation of your Trust Assembly ideas! 😍
Your prose in earlier posts helped to catch my interest but it’s really the technical details that enable others to see whether your ideas are pie-in-the-sky dreams or actually something worth investing time into understanding, sharing and contributing to. :)
Just speaking anecdotally: There are multiple technically-minded friends with an interest in improving societal discourse that I’ve found it difficult to share your longer prose about the Trust Assembly with. The details there are so vague that it’s hard at a glance to see whether your ideas could actually work when implemented or if they’re just whishful thinking with deal-breaking flaws in it. Being able to refer them to a technical write-up does so much to communicate “this is trust-worthy bc. you can verify for yourself if the ideas make sense”.
If you worry that the technical descriptions are too il-fitting on your blog, why not create a website that hosts all the technical information for those interested? Then you could refer to it repeatedly on this blog where you can keep the focus on communication the Trust Assembly idea to a wider audience via story-telling and big-picture ideas.
I think with my hands. I think that’s why I’m a better writer than speaker. One thing I’ve discovered in my life is that I’m weirdly good at putting a whole process together immediately in my head and knowing with high confidence if it will work or not, and less good at explaining it to everyone else in detail. Only reason I feel that isn’t delusion is because if I can manipulate physical things with my hands it becomes immediately obvious I have a model in my head I’m working from. I’m trying to bridge that gap.
I'm not techy enough to understand any of the dev stuff, but I'd love to be a part of this. If user testing is helpful, I'd join an alpha version.
My Wikipedia moderator cabal and me are very excited to get our hands on this one
Man I hate wikis. So damn hard to maintain. At least markdown makes life easier.
Damnit I love LaTeX.
I have memory challenges. Will mail you bundle of scrap paper, back of envelopes, and post its.