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.

Replies (1)

Spot on. IMHO … the essential elements are: - “is trusted” should be explicitly determined by end users. - “filters” that operate from “is trusted” should be subscribable and sharable by end users across all apps. Using this simple architecture, “filters” may “ingest” any data or metadata from the network to satisfy for ALL of the diversity of “WoT algorithms” that smart people like yourself have designed. - use filters for content feeds - use filters for recommendations - use filters to manage the “is trusted” list itself, so a user doesn’t have to. 🤯 What are your essential elements?