thinking about adding a "filter" to nostrdb's query interface. basic idea is that you can provide additional filtering or reducing logic in any nostr query.
I like this better than setting a large limit and filtering after. you can just let #nostrdb do it while it scans the index.
I want to use this for ignoring thread replies, which is useful for building ai algos that try to summarize the past day or specific days, etc.
In the future we could support a jit-compiled jq-style language and use that in the callback:
{"kinds": [1], "filter": "not tag('e')[2] == 'reply'"}
#asknostr if you are a nostr dev, would you use this? what would you use it for?
how can anyone use it at all?
Please Login to reply.
what do you mean?
nostrdb has rust bindings so you can use it in any rust app on any platform. it's also written in C and can bind to any native nostr application (android, swift, desktop, etc). just not the web because the web sucks.
that's what I meant
