Open jiftechnify opened 3 months ago
More intuitive filter syntax
On this note, it would definitely be better if it accepted a standard filter object and then nostr-fetch
validated/extracted the prerequisite properties from the filter internally, as opposed to splitting the filter into filter
and time-range
Another thing that comes to mind is that the relaysUrl
argument is unintuitive/confusing/unclear when using an adapter with an existing pool, for example NDK.
... any ideas?