It works for us. Here’s how it works:

You go to a Brainstorm instance, such as my prototype at straycat.brainstorm.social. Click the button to sign up and to sign a user preference 10040 event, which basically says “brainstorm is my WoT Service Provider.” We create a new brainstorm nsec just for you, like a franzap alter ego, which we’ll use to publish scores on your behalf. (We may need to publish updated scores when you’re offline, so doesn’t work to publish straight from your pubkey.) We calculate personalized GrapeRank from your perspective, like PageRank but uses more than just follows. This produces a 0-100 Trust Score for every pubkey in nostr. For everyone whose score is above a cutoff like 1 or 2, which usually is about 130k pubkeys, we publish one kind 30382 Trusted Assertion to a dedicated TA relay, which contains multiple scores including GrapeRank, PageRank, distance from you in hops, and counts of verified followers and verified reporters.

It sounds like too many events to be feasible, but it’s not really. It works. The 10040 event tells the client (Amethyst or zapstore) where to find scores from your perspective. All it needs are your alter-ego pubkey and the relay with the TAs. The beauty is that zapstore has no way of knowing whether your TAs come from Brainstorm or Vertex (if I can ever convince pip to use TAs) or relatr (which is also using TAs) or whatever other WoT Service Provider comes along. So if law enforcement tells you that zapstore needs to stop support for Vertex bc they’re not whitelisted, you can say zapstore doesn’t integrate directly with score producers bc that’s not how TAs work.

As a user, you don’t have to know how any of this works. You just click a button and 10 minutes later you see a 0-100 Trust Metric over every profile pic on Amethyst. It’s personalized, like personalized PageRank, but has an actual, workable fix to the link farm attack that is the fatal flaw of PageRank.