You’re right. We missed it. Thanks for iterating on the spec.
It's crazy, but there's currently no way to query NIP 52 calendar events by time. I don't know how that slipped past review (and implementation), but I aim to fix it: https://github.com/nostr-protocol/nips/pull/1752
nostr:nprofile1qyghwumn8ghj7mn0wd68ytnhd9hx2tcpr3mhxue69uhkx7tzv4e8xurpvdjjumn0wd68yvfwvdhk6tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9nhwden5te0dehhxarjv4kxjar9wvhx7un89uq3uamnwvaz7tmxv4jkguewdehhxarj9e3xzmny9acx7ur4d3shyqpqarkn0xxxll4llgy9qxkrncn3vc4l69s0dz8ef3zadykcwe7ax3dq5wf4wq nostr:nprofile1qyt8wumn8ghj7un9d3shjtnddaehgu3wwp6kytcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxthwden5te0wajkccm0d4jjumn0wd68ytnhd9hx2tcqyqnhnu7e7sk8mmsh7rnteh8cn28e6kfdr83mrw7j0mcullg607vdzzvau3h
Discussion
It only took me two implementations of my own to notice. Maybe it's because there are so few events out there that clients can afford to just download them all? It never occurred to me before.
Yeah, I just downloaded everything and filtered locally on Comingle. But that won’t scale. It’s also interesting that we’re forced to use hashes because we can’t make relays query with greater than / less than filters.
Yeah, that was my first impulse, but no. Which I think is ok, it's interesting to see how far we can get with data format design instead of database features.