franzap on Nostr: No, Zapstore never calculated any of this client side. I could do the intersection ...
No, Zapstore never calculated any of this client side. I could do the intersection but it's too much processing and bandwidth, all without any Pagerank sorting. Awful UX.
I used to have an API service powered by Memgraph, pretty sure we discussed it.
And now, about to launch Vertex (nprofile…prv3) which is DVM-based and currently being tested out in the latest Zapstore. It supports personalized Pagerank and it's blazing fast. This is what I've been building with pippellia (nprofile…pqkh) , which I also thought you knew?
I asked you earlier because I wanted to know how you'd approach the Zapstore usecase purely with NIP-85, as I didn't (and still don't) see how that is better than a DVM.
I used to have an API service powered by Memgraph, pretty sure we discussed it.
And now, about to launch Vertex (nprofile…prv3) which is DVM-based and currently being tested out in the latest Zapstore. It supports personalized Pagerank and it's blazing fast. This is what I've been building with pippellia (nprofile…pqkh) , which I also thought you knew?
I asked you earlier because I wanted to know how you'd approach the Zapstore usecase purely with NIP-85, as I didn't (and still don't) see how that is better than a DVM.