Tapestry protocol - curation of decentralized digital tools by the web of trust - progress report:

Still a lot of tapestry implementation proposals (TIPs) to add and expand just to reflect the two proof of concept apps that I’ve already built.

I decided yesterday to reorganize the protocol by moving a chunk of it into its own section, one that details how data structures are curated, organized by data model.

One of the most basic data models is a “simple list”, the curation of which is live and functional in my (buggy) desktop app, Pretty Good Apps. A more complex data model is a graph, the curation of which I have not built as a proof of concept, but it will be a simple matter to extrapolate what already works for simple lists. Eventually, data models will be designed that are complex enough to allow us to curate the entire protocols for nostr and for the tapestry protocol itself!

Each data model has its own challenges and design decisions. Which elements can be curated independently of the others? Which elements are interdependent and must be bundled together and curated as bundles or modules? There’s often no single “right” answer to many of these questions. Fortunately, questions like this — ones with many “right” answers, and which answer we pick is arbitrary — are precisely the ones that the tapestry protocol is designed to tackle.

So much work to do.