It’s not gonna be one size fits all. I look forward to seeing the DVM specs!
It is a lot of data. But the question is this: do we calculate WoT scores on the fly just when we need them? Or ahead of time? Right now, we’re trying to do all of them on the fly. I think that’s great for some use cases, but it places severe limitations on what we can accomplish. If we want the notion of WoT to mature, some calculations are simply gonna have to be done ahead of time.
Per NIP-85: there is one event which holds multiple personalized WoT scores (I export GrapeRank, PageRank, & hops, with more scores to be added later) per pubkey. So that’s one event with multiple WoT scores, all concerning Alice, from the perspective of Bob. (“Personalized” means from the perspective of Bob, as opposed to “global” which really just means from the perspective of a big centralized entity like Google.)
We can have third party services to generate and store these events. Right now my app exports these events to my relay. But my vision is personalized WoT relays where Bob will store all of the events that are calculated from his perspective. NIP-85 provides a way for Bob to tell clients where to look for any given WoT score (kind 10040 notes), which can be a personalized WoT relay, a third party service, wherever.
So I see this as basic division of labor. Let each app do what it does best without also necessarily having to provide a complete WoT solution from scratch all by itself.
