WoT is a heuristic, it doesn't need to be exhaustive. One way to state the goal is to remove 98% of what the user doesn't want to see, and produce recommendations that are more than 10% likely to be relevant. Implicit web of trust is enough for that. Explicit additions may be a useful addition, but probably won't ever result in more than a 1% improvement (still huge) over either metric above.

Replies (1)

Now that is nice! I’d love to see those numbers. But there’s more to consider in a real world “trusted” WoT implementation (at scale, on a network whose new user retention will entirely depend on them being “included” at day one into a “trusted” network) than a quantified difference between algo derived WoT lists and “human in charge” WoT lists. Because WoT will likely end up first in line during new user orientation, and talked about constantly (Custom content filters are already a claim to fame for bluesky, and Nostr’s will be even better.) the tools for implementing WoT will need to also be front and center. Easy to understand, discover, and use. IMHO, giving people an “is trusted” checkbox for their follows, and saying “this controls your web of trust” will be the ideal on-ramp for getting them to the understand that (client configurable) content filters are ALSO working behind the scenes suggesting their “trustworthy” sources. What I’m pointing out is a UX flow for getting people to make use of WoT, so that nostr can survive the long haul. This is the “other thing to consider”.