I have a basic search API working locally now as well using https://search.nostr.wine as the backend. It accepts get requests with optional parameters search (string), kind, pubkey, since, and until.

For example: ?search=cookie&kind=1&since=1680121746 would return any matching kind 1 events in the last 24hours where “cookie” was seen in “content” in json. Would anyone want to use this?

Reply to this note

Please Login to reply.

Discussion

Very cool! Possibly, it's not the way I think search should be done ultimately, but it could be a good step toward a complete solution

We will offer NIP-50 as well just throwing out as many options as possible. Kibana for people who don’t want to use an API, a web option for people who do, and nostr native for the rest.

Also very open to any ideas you might have regarding the future of search if you’d like to share!

Side question: does coracle support NIP-42? I just wrote basic on connection AUTH and would like to try it with some clients.

Awesome! so is this like a custom form of the NIP-50 keyword search that relays can support?

I’ll support NIP-50 as well so that nobody needs to change any existing integrations. Just wanted to offer a web option as well since it’s easy to expose.

Kibana, API param query, or NIP-50 should all give you the same results. Dealers choice!

Added limit and page args. This will allow pagination when using different sorting methods besides time (like search term relevance).

Should be able to launch the first version of this tomorrow. I’m thinking it will live at api.nostr.wine/search. I’ll write some documentation when I get a chance.

#[0]