Thread

So maybe we’re doing basically the same thing, except I’m using NIP-85 and you’re using DVMs. To me, DVMs seem too complicated. But in all fairness I’ve never tried building with DVMs. Having calculated the WoT scores, it didn’t take me long at all to make a button to format and publish the data as kind 30382 notes, plus one kind 10040 note. That’s all that NIP-85 requires. I suppose DVMs will be useful if I want to make money as a third party WoT service provider. But if I want to calculate WoT scores myself, using my own personalized WoT relay, is the complexity of a DVM really necessary?

DVMs are not the perfect design but honestly it's not that hard. Instead of sending a REQ you publish a signed request event. I never tried building a WoT relay so I don't know. Besides DVMs and the monetization, it makes sense to me for this to be a service rather than precomputed events for the use-cases that clients have (verifying reputation, sorting, recommending follows, etc). Are you going to keep 30382 events for all permutations of pubkeys, for all services, sorted by all different algos, and all reflecting the latest updates to contact lists? A service really is most suited tor this kind of thing, imo. Also, kind 30382 is too generic and not expressive enough for our needs. If you'd like, tell me how I would use those to replicate the WoT i currently have on Zapstore (follows who follow). Are you familiar with that? No, it's not recommended follows. It's who of my follows, follow the signer of an app, sorted and limited to top 5. We can continue the discussion next week when I publish the DVM PRs, as I would love to hear your input and if it could potentially work for your usecase and algos