Replying to Avatar Vitor Pamplona

Here's a question for you. I was considering a replaceable event that is updated by the provider all the time as opposed to a request/response procedure protocol.

A replaceable event will be easier to code by clients (just subscribe to event x) but I didn't know if it made sense for providers to keep updating a list of recommendations every time a new post comes into the list.

Now that you have coded it, do you think the request/response procedure was a good choice?
Avatar
brugeman 2y ago

I think it's kind of annoying to code this RPC, I have to juggle with relays like all clients do, and it adds a lot to latency. I could just publish NIP-51 list w/ trending stuff periodically on some number of relays and achieve the same goal. But that's only for global trending stuff which is not updated too often and is same for everyone.

But when it comes to personalized recommendations - RPC allows you to pass parameters. I tried doing a specialized relay like data.nostr.band, but that has lots of other problems, I don't like that route.

So I think this RPC style is superior and is a great idea, we just need to build good tools to manage relays and keep persistent connections to reduce latency.

Reply to this note

Please Login to reply.

Discussion

No replies yet.