build relays that do the searches efficiently.

Do not underestimate client-side verification. Privacy also much harder with trusted WoT services. WoT Providers should be optional and ancillary to client-side processing of events. Also, do you think WoT is not portable when it is calculated client-side? It is open-source code we are talking about. Anyone can use the same algo. So: 1. Depends on requirements. Global is much faster and cheaper, but less about you. Should be left to the user. #Vertex does exactly this 2. Standardization I welcome. But there are trade-offs to third-party WoT see on top 3. Yes, user choice is welcome to the degree a non-technical user is NOT left to his own devices by default 4. Agree - privacy is most achievable with client-side calculations or self-hosted services which will be very niche

I should probably clarify: I don’t mean to say that client side calculations should NEVER happen. I mean only that client side should not be the ONLY option. There are many instances where it would make sense to do a mixture of both at the same time. Example: an e-commerce client with average 5-star ratings. It would make sense to me for the 5-star product ratings to be calculated by the client, but the client uses something like the rank score calculated elsewhere to remove ratings authored by bad actors. So the e-commerce client calculates 5-star ratings on the fly, which is not hard bc there’s (usually) not a lot of data involved in the calculation, and uses them locally. But the client could have the option to publish those average ratings using a format like trusted lists, so that I can use those scores elsewhere (or maybe use the locally repeatedly without the need to recalculate each time I navigate back to the same page), in which case the e-commerce site is serving as a mini service provider.

On item 3: As a user I want to switch back and forth between vertex, brainstorm, relatr, trustr, etc. This should be easy, good UX, no technical expertise. Suppose I want to go to zapstore and switch from vertex to another SP (which supports DVMs, for the sake of argument). How does this happen?

WoT scores calculated by primal are much less portable than WoT scores calculated by brainstorm/vertex/relatr/trustr and consumed by amethyst/primal/damus.

Point 4: by privacy in this context, I mean I don’t want zapstore/damus/amethyst/primal devs to tell me that PageRank is the only algo they support, or even to know which algos or parameters I am using. The only way for that to happen is if the scores are calculated elsewhere. NIP-85 Trusted Assertions was designed with this in mind.