Just keep in mind subscription event result reads can be easily faked/spammed too.
Discussion
You mean receiving a bunch of pointless/extra/wasteful reads? Seems like something worthy of tracking
I’m sure you can get some insights out of it for operations. Can even help with database optimisations around partitioning, indexes, etc.
However, if your looking to charge per event impression for example, it’s unreliable as a ‘event has been requested/viewed X times’ metric.
I'm only really interested in the former. Hadn't considered charging *per* read or impression. Seems hard to measure given what you've said.
I mention it mostly because the ‘impression’ metric is largely related to todays advertising business models.
At some point someone is going to want to try tracking impressions or a derivative and charging - ideally it’s unworkable and fails. Advertising is a burden on society.
And certainly Nostr will always be read biased. More likely 100-10000x as it grows.