Yes the count query seems like the obvious fix here. I just haven’t seen it implemented in any client yet, no idea if any Relay even support it yet. A count query has its limitation too, you have to blindly trust the relay, and have to choose only one because you can’t deduplicate 2 different count response. Cannot verify event signature too obviously. But I agree the count query will become mandatory at some point. It just seems like this kind of query is not a relay job but more a @Vertex one, just like follow count.

Replies (2)

There is NIP-45 for counts, but it's not widely supported and it's quite cumbersome for relays as it probably requires a separate tags table, and some indices as well. I know because I've built my own. Anyway, I kinda agree, adding too much features to relays reduces one of the best feature of nostr: simplicity.
There is NIP-45 for counts, but it's not widely supported and it's quite cumbersome for relays as it probably requires a separate tags table, and some indices as well. I know because I've built my own. Anyway, I kinda agree, adding too much features to relays reduces one of the best feature of nostr: simplicity.