Gzuuus's avatar
Gzuuus gzuuus@nostree.me 1 month ago
Hey! Not exactly. Nothing is computed client side, the client simply makes a call to a Relatr server. The server computes the trust score based on social graph distance and custom validations. So yes, the scores are calculated by the service provider independently of clients . As we discussed a few days ago, we are considering adding trusted assertions to the mix. This way, a client can choose to either fetch published trusted assertions, call the server, or do both depending on it's needs
↑ Parent

Replies (1)

david's avatar
david david@bitcoinpark.com 1 month ago
Ah yes, that makes sense. The communication between client and relatr server is performed via a model context protocol API, correct? Is there a document with the MCP API spec, and would it work to turn it into a NIP? If I understand correctly (and again, correct me if I’m wrong) you’ve designed it so the communication is done under the hood, meaning the dev doesn’t have to know how the API works, and this is to make life as easy as possible for the dev who wants to implement relatr. So Vitor’s idea is this: what if I want my users to have the option to redirect their API from Alice’s relatr server to Bob’s relatr server to some other WoT Service Provider that’s not necessarily relatr (maybe it’s Brainstorm, maybe it’s Vertex, maybe some other WoT SP)? The challenge would be to make a generic API that supports multiple WoT Service Providers that may or may not calculate the same metrics in the same formats. Trusted Assertions handles this challenge well, and a WoT API should be able to do the same. What do you think? Can your MCP API spec be morphed into a Nostr WoT Connect NIP?
↑