aaron on Nostr: I verified this was an issue on my side. Recently I separated my query indices from ...

I verified this was an issue on my side. Recently I separated my query indices from my event store. Since this is a super old message, and due to a data truncation I did a while back, my event store had this event, but my index did not. Which is why the write answered it was a "duplicate", but the event did not come back in the query (which uses the indexes). Thanks for looking into this, which helped me identify the cause. Sent you a beer in sats. Cheers.