Vertex's avatar
Vertex 11 months ago
Interesting. Again - what's the usecase you have in mind? Showing relevant who follow? For precomputed to work you'd have to generate ranks for all possible permutations of pubkeys? @Pip the WoT guy do you have any idea how many those would be for Personalized Pagerank? We have a DVM that sorts authors. You give it a bunch of authors of comments, and it returns them sorted by rank. How do you do that with NIP-85?

Replies (3)

Suppose Alice is the logged in user, and you have a list of authors A_I that you wish to sort by rank. Step 1: find Alice’s 10040 note, which tells the client where to find her kind 3038x notes. (If not available, use the platform’s default 10040.) Step 2: for each author A_i, fetch one kind 30382 and extract the score using the “rank” tag. Use that score to sort.
Any given service - Grapevine, Vertex, etc - will have customers. For each customer, let’s assume on the order of 10^5 to 10^6 kind 30382 notes. Each note contains multiple WoT scores. Your service updates these notes periodically and stores them in a relay server. Different levels of service exist with higher levels of service meaning more notes per customer, more scores per note, more frequent updates. Future: all of the above, but managed by a personalized WoT relay.
Follower count, for instance. Only needs to update when a new follows are added or deleted from the user. Then the replaceable event is updated automatically. No need to request a DVM for it. It's already on the phone