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
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? nostr:nprofile1qyt8wumn8ghj7ct4w35zumn0wd68yvfwvdhk6tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ehx7um5wghxyctwvshsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszxthwden5te0wfjkccte9eekummjwsh8xmmrd9skctcpzemhxue69uhk6mr9dd6juun9v9k8jtnvdakz7qpq76p7sup477k5738qhxx0hk2n0cty2k5je5uvalzvkvwmw4tltmeqrtmus0 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?
Discussion
The kind 30382 event gets updated with the new follower count by the service and the phone sees that automatically.
Then if the user wants to see the actual list of followers, the client will access the service via the DVM for the list of pubkeys.
That makes sense to me.