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.

Replies (1)

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.