hodlbod on Nostr: That works well for local queries or for relays that support map/reduce (which is a ...

That works well for local queries or for relays that support map/reduce (which is a good idea), but less well for generic remote relay access, at least in the short term. My approach is to generate efficient queries rather than post process, which is mostly doable.

It seems like regardless of fetching strategy nostrscript and my nip are representing basically the same stuff, so as long as they could be compiled into one another they could be considered equivalent.

Does nostrscript have a spec yet? Until it's more widely available to developers it sort of fails the interoperability test. It's not trivial to write an interpreter for custom feeds either, but it's more accessible since there's no parsing step required.