#[0] hey I noticed on the snort search integration if there are no results found for the search it keeps trying with different since/until filters every second. Very spammy on the relay side as search REQs are much more expensive than others. Anything we can do about this to reduce the number of requests?
I may have to add search specific rate limiting but would prefer to wait on that for now.
very good point raised for all #nostr client apps in fact - many apps need to provide better UI search options and later advanced #search - if any user try abuse or DDOS query on relay servers then yes ratelimiting (based on affordability n tolerance of each relays admins) comes into effect
i tried GUI based search engines - like nostrview.com best so far
If you make your first request without any since/until, we’ll return results by recency anyway and then you can paginate using the last created_at timestamp.
Yea it's broken right now so it doesn't normally do that
Charge for it. Seriously.
We accomplish our custom features by putting our own service in front of Strfry instead of trying to modify strfry constantly to fit our needs. First, we aren’t C++ devs but more importantly the reason Strfry is so performant is because of the thoughtful design decisions Doug made. Wouldn’t take long for us to destroy that if we started messing with the architecture.
That’s the way I would approach this project too.
