max_ns on Nostr: i like this a lot, been thinking about composability in general and specifically ...
i like this a lot, been thinking about composability in general and specifically about discoverability and relay logic
lists are the closest, but as you say, they're generic, and making per-user lists would be unwieldy
complicating relays in this is a big departure from being 'dumb'
so i wonder if optional 'indexers' are the way, i think many clients are already doing it (certainly primal), and everyone keeps doing it their own way, we'll eventually see the clients become walled gardens
ofcourse the downside is that indexers become de-facto sources for most, but as long as they're easy to implement/stand up (i'm even thinking in-browser personal indexers), the same argument used for relays is used for indexers - and there's always the option of just querying relays directly
the upside of shareable feed logic and the reduction of loads on relays due to indexers aggregating (most of) the querying feels worth it
lists are the closest, but as you say, they're generic, and making per-user lists would be unwieldy
complicating relays in this is a big departure from being 'dumb'
so i wonder if optional 'indexers' are the way, i think many clients are already doing it (certainly primal), and everyone keeps doing it their own way, we'll eventually see the clients become walled gardens
ofcourse the downside is that indexers become de-facto sources for most, but as long as they're easy to implement/stand up (i'm even thinking in-browser personal indexers), the same argument used for relays is used for indexers - and there's always the option of just querying relays directly
the upside of shareable feed logic and the reduction of loads on relays due to indexers aggregating (most of) the querying feels worth it