Replying to Avatar Laeserin

Yeah, it's why Jumble works quite smoothly, even though it's "only" a web app. Just slow-drips in the feed from 1-n relays and basta.

I don't "follow" a lot of people on my Kind 3 list, which means those few people get a noticeable WoT bump from me. Those are clearly npubs I am _actively recommending_.

I added a "lists" filter to the feed, and it reqs for the deduplicated aggregate list of all npub lists I select.
Avatar
Laeserin 5mo ago

The thing people mess up with lists, is that they don't force-fetch the req.

So, if I am looking at theforest feed and select the nostrdevs feed, it should

* figure out which npubs aren't included in TheForest feed (most/some of the list is probably included, as people tend to share relays with their frens),

* use outboxes, relay hints from their cached notes, NIP-05 relays, and/or aggregators to go out and hunt down _everything_ from those npubs, and update the map. Then the map is theforest-events + list-events, and the list events req is quite small.

Reply to this note

Please Login to reply.

Discussion

Avatar
Laeserin 5mo ago

Nostrdevs list, I mean. In other words, I expand the current feed with whomever is not already there.

You could also look at the list feed, alone, but leaving it like that, permanently, is why feeds get ossified. Opinionated and/or paid relays create a steady trickling-in of new npubs, that enrich the feed, while the list makes sure you don't miss your faves.