The HN search help page⁽¹⁾ still documents points>NUMBER as a supported filter, so hopefully this is an unintentional regression.
⁽¹⁾ https://hn.algolia.com/api
mmakeev4 days ago
i hit the same 400 querying the algolia, a raw > in the query string is what does it, encode it as %3E and points>100 comes back fine for me right now. curl -G with --data-urlencode handles the escaping if youd rather not do it by hand
eddygop4 days ago
Thanks for the reply!
I went to make the change, and all the sudden it started working with “>” again (not URL encoded) so this appears to have been a transient issue.