Relatr already does it @Relatr 🤙

Yes, I was asking about the relationship between the provider and the user who declares that provider. When brainstorm generates a new key pair to start publishing TAs for a user, does that new key pair have some context? For example, is there a kind of identifier, like a kind 0 or similar, that indicates 'This public key is the publisher of TAs from the perspective of user_pubkey'? I'm trying to understand if there is a way to determine which provider belongs to whose perspective. I hope this clarifies my question. Let me know if it is still unclear

Dame caña

You really like monkeys! hahaha

And printers hate you!

A ok, seems that there is a mcp server, but it is just an interface for nostr so user can lookup and reserve (?) . Anyways, this doesnt seems related at all with mcp ui, which is basically a mcp server side rendering an interface

Im struggling to follow up in this convo. What communicates with nostr via mcp server? Synvya? 🤔

Not sure tbh. I doesn't seems to talk about new ways to conceive apps, just an ai adds service

No idea what synvya is

Yes, two interfaces different use cases. TAs might work better for caching and clients that rely on the producer-consumer pattern (producers publish all, consumers can get these async anytime). Request/response patterns also work for that, but some people might argue that it is more complex (?) In any case, I think Relatr is the only service out there that satisfies both interfaces. It can be configured to publish TAs and it naturally fits into the request/response pattern through CVM. It also supports range lookups for a list of public keys.
https://www.contextvm.org/s/750682303c9f0ddad75941b49edc9d46e3ed306b9ee3335338a21a3e404c5fa3

Yea I think relatr and brainstorm are the only ta providers out there (afaik). And brainstorm spins up a new pubkey for each user that signup so there is no single service pubkey. I don't know if there is some way to map the new pubkeys to users, maybe @david can help us here