Can anyone point me in the right direction for ideas / thoughts / implementation for WoT on Nostr ?
nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc
Can anyone point me in the right direction for ideas / thoughts / implementation for WoT on Nostr ?
nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc
Following
Old.iris.to has the slider - show me only one hop, two hops, three hops away etc..
Some apps, I think coracle is one of them, somehow calculate a WOT score of sorts.
Damus has notification friends toggle, and a show shared follows in profile view.
nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8 adds WOT to the appstore - which of my friends follow, or verify an apps sha256 hash..

I created an API that returns top 5 of your "following-who-follow-x" sorted by PageRank.
For example this is how we both connect: https://zap.store/api/trust/npub1dtgg8yk3h23ldlm6jsy79tz723p4sun9mz62tqwxqe7c363szkzqm8up6m/npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9
(Give it a little time, it's slow right now)
Our connections with higher signal on our social graph are nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft and others (you follow them and they follow me)
Why an API, when all other approaches do it client-side? IMO makes no sense to pull a ton of data and heavy calculation client-side, certainly with less awareness of weights in the social graph. With this API you get a small number of npubs you can then pull contact lists from client side and verify the API is not bullshitting you.
I am currently working on making it way faster (will use a more specialized DB). Let me know if this interests you
Awesome !!
Parallel thoughts ^there. Centralized implementation of the tool through a limiting idea, principle, or structure that the engineer has in mind is a non-starter. It must MUST be an entirely different trust score for each individual, based on the individual's choices. And we must discourage wholesale adoption of standard trust data during onboarding at every turn, ensuring a seed for each user that allows for ownership of one's own discernment, rather than delegation to a one-click preset that threatens to defeat the purpose.