Yeah, it *is a lot of events.  But, it's either that, or do it over API calls like I currently am doing.. I've since capitulated to using events because it will provide better uptime and redundancy when a 'provider engine' goes offline or something.  I have about 185k nip85 events for my pubkey that I reference.  I *can share this with others (ie, they use my calculations), then that's less that need to be published (basically they don't need to sign up).  This is what I assume you are talking about is everyone using this same set of events.  That seems ok depending on what you're doing.  But why should I trust *your scores of app creators when I could make my own, or etc.  It does seem like eventually you want to calculate your own perspective of the network.

For my use case of using these for relay access control, I have to read ALL the events, so none go un-used..  There are probably other use cases that don't need all of them but they're there.  Mirroring 185k events to my own personal relay for saving it away also, seems like not that bad.. But, I deal with a LOT of waste on nostr relays so it's possible that I duno, we took some crazy pills already.