It filters based on min zaps, excluded words, and things like that, you can’t really do that without a custom relay as relays aren’t really supposed to know about zaps.
nip50 was nice because it standardizes fulltext search, so i could make damus local search compatible with relays. I can’t really do min zap advanced search “properly” without a relay nip, but i can hack it with nostrdb at least, and just try to pull down as much data as possible.
Oh you mean you can’t send a REQ with this level of detail.
i thought they were pulling what they can pull at the level the relay can understand from a REQ and then applying the filter on client side.
or at least everyone else can do that. I thought that’s the idea of having a local relay and a DB. You can cut slice and filter as your please, no?
You can do that but it wouldn’t be very efficient and you would get fewer results, and wouldn’t scale. They will have to do it on their relay if they aren’t already. We can do it locally but there is no corresponding remote REQ we can execute to get the data. Maybe just negentropy syncing all the zaps for the day would work well enough for a little while.
