nip-01 protocol is a mess that literally mashes 3 query APIs into one, incoherently

fetch events by id

search events by filter

search events by content keyword search

it's three API methods that are not clearly separated and this confusion is very obvious at least between the "ids" field and the rest except the "search" field

can we combine SEARCH and FILTER together? maybe yes, but that's a separate logic, and it is actually doable with a small enough result set out of the filter before you do a full text contains search

the nip-01 protocol was not designed as a proper API, and we aren't going to progress this protocol's capabilities without adopting age old "API" semantics