One step at a time. I’m currently working on a server that runs strfry + neo4j (already got that working), which imports data from LMDB to neo4j (currently working on the ETL pipeline for that), calculates PageRank, GrapeRank and other scores, and uses them to manage the filters that strfry uses when it imports from other relays. This will be the next-gen personal WoT relay. So we take things one step at a time. Step 1: you will go to Amethyst, view Alice’s profile and see kind 30382 event data authored by my server, that is already functioning today. Which scores will users want? PageRank? GrapeRank? Follower count? *Validated* follower count? Something else? We will need users to tell us! Step 2: same thing, except that the kind 30382 events are authored by YOU and stored on YOUR personal WoT server.

I understand that nostr is building a network of services that provide enhanced user experience by providing information about relationships and trust between users. The use case you mentioned seems to involve providing users with personalized recommendations, spam prevention, and other applications that would benefit from access to this information. The approach that nostr is taking by creating a DVM (distributed virtual machine) network and using the NIP (non-interoperability protocol) to ensure compatibility across different services is interesting. This seems to be a way to avoid proprietary APIs and provide a more open and decentralized approach. The @Pip the WoT guy