Yes, please.
Discussion
IT'S A HUGE PROBLEM THAT NEEDS TO BE FIXED.
So is there a solution here where the local clients (?) store an index of the records pulled down and share that between clients in interoperable way so they don’t need to pull the same record down more than once even if you have more than one client or more than one relay that’s accessing the same record? Or perhaps this could be done as an added service where your verified user ID is? Maybe that’s one reason to pay for a verified user ID to get this kind of collection parsing?
wowser
see, that's why i paid for 2 relays, nostr.wine and nostr.land, and at best i also use nostr.band and damus.io relays (not their actual addresses dammit)
if you use 10 relays you use 10x the traffic, i only use those two free ones because i have found that i don't get quite enough coverage from the two paid relays
and yes, as people in parallel replying here point out - this is one of the things that #gossip / #outbox solves because it reduces the amount of replication of data, AND the reduction of the number of relays you have to ask for a given event
i would cut out the two free relays altogether if NIP-65 were widely supported by clients
i don't know what the two paid relay guys have exactly got set up for NIP-42 either, and whether they are pulling events to fill the gaps, tbh i'm not that confident these issues are solved
the sooner everyone gets NIP-42 and NIP-65 properly implemented, the sooner we can all have nice things