mleku on Nostr: making a custom search to enable faster processing of social graphs is a possibility, ...

making a custom search to enable faster processing of social graphs is a possibility, but it would be a new endpoint

unlike the silly nips scheme, with meaningless numbers, the APIs i envision are named, and use a standard naming scheme, so you could have a custom endpoint that does some kind of specific ordering as per the requirements of vertex

like, i'm envisioning things like a query that specifically is scanning profile/mute/follow lists and a specific key structure that lets you implement multiple sorts of these on the relay side before actually fetching them, like clustering the results so you get them in a sequence profile/follow/mute for each one, but this is already a simple one based on an author sort, something that was in my mind

this one requires a second index of pubkey to profile event so you or something along these lines, i was thinking about this, for the filter endpoint, to enable sorting them by pubkeys as well

a query that is specialised for social graph analysis totally could be done, just tell me what you think it should do and i can come up with a key layout that enables this search to be optimized for