Nope. Only the solutions I could think of require a spec update, like yours on the relay side, or on the client side we need to start including an indexable tag with the address/aTag
Discussion
how would this work? isn't the `#d` tag already indexable?
He means adding 'a' tags to the target events and querying them via '#a', that may work in some scenarios
Yes but thinking about it a bit more now, it wouldn't be a good solution because anyone could create the same 'a' tag and mess up your results on purpose.
My use case was the same as a few other feeds I have, where I fetch reactions from my follows, then do a single query with 50-100 ids to build feed based on those reactions.
I wanted to do the same for Articles (kind 30023), almost had it ready until I realized I can't query 50-100 article aTags in one go.
Agree. And there is zero clarity on limits really, so 50-100 is just kinda shooting in the dark and hope relays return enough and keep iterating.
Just wrote this, and actually would be great if relays could via NIP-11 inform what's a maximum amount of accepted ids in the req.