Yes … tapestry is nice … you have obviously put lots of time and effort … BUT it does carry a lot of assumptions about “trust” that might be better left to the free market. IOW… actual WoT NIP for nostr could be even simpler… describing a standard for subscribable filters by which end users could choose the “trust” assumptions that work for them. Scalable WoT solution will be simple and not cumbersome for developers or end users… with minimal assumptions about HOW trust should be determined.

Replies (1)

Scalable WoT definitely needs to be intuitive and easy for the users. Design is going to be of utmost importance. As for the developers, the question is how to make it as easy as possible and still get the job done. There is a reason that WoT has failed to live up to expectations for the > 3 decades we have been trying to make it work, ever since PGP was introduced in 1991. In my mind, WoT is like an airplane, in the sense that if we want it to fly, there are certain elements that must be in place. Omit just one essential element and it will never get off the ground. For too long we have been too lazy to accept that fact and figure out what those elements are. And that’s what the tapestry protocol is about.