Another use case for the grapevine score: order of users when searching for them
The current NIP-51 list exported at
http://grapevine.my
omits pubkeys you’re already following. For this application, you’d want the list to include those pubkeys.
@cloud fodder ,
@ManiMe , we will need to standardize d-tags so clients know which NIP-51 grapevine list to pick for any given application. nostr:note1hqstvqd7rk9cp9r80yywkvs0s9nt2kn2u9n8rw49vla2wnr56svshrrlt6
priority could be:
- who i follow
- WoT
- high follower count
- alphabetical
Take the grapevine score list, shift your follows to the top, and that’s very close to what you’d get. Although tbh it might be even better without doing the shift.
The advantage of the grapevine scores list is that the client can (soon - not quite yet) import it as a NIP-51 list or set of lists. Might be faster than the client calculating it on the fly.
David. I think you’re onto something really big here… but the iceberg goes deep.
- The use case for “auto generated lists” (as we are imagining) is novel to Nostr. It’s not exactly “covered” by design in the NIP51 spec nor accounted for by any client developer.
- and even as they are, lists are not really used by clients in ways that they could or should be.
- these two facts go hand in hand … because lists are assumed to be “made by hand” then clients don’t implement them as data stores for various needs, because that would too much to ask of end users.
- so there’s a paradigm shift we’re up against which will be more work to change than just designing a “d tag standard”.
But also… that’s a good idea. 👍🏼
This is very insightful. I hadn’t thought of it quite that way.
My naive impulse is to store many pieces of info in the d-tag, as dictated by the fact that the d tag is what’s used to update NIP-51 lists, but then to store each or every of those pieces in their own customized tags if we think a client may want to search based on those tags. I have used this technique in my initial nostr implementations of the concept graph.
And when that gets too complicated … I have solutions but I don’t want to go there yet. Way too deep for this thread. We won’t solve everything at the stage we’re at right now.
What do you think of my naive impulse? Keeping in mind that our immediate path forward must address the paradigm shift you mention.
btw have you taken a look at the d-tags when you create a new list on listr? Non human readable. I think that may be inevitable for us.
Oddbean new post about login | logout