You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 14, 2024. It is now read-only.
I will definitely implement a search against the local database but probably not nip50 because it is not widely supported. I just checked the 10 relays with the lowest latency for me and none of them advertised nip50 support. This might change in the future so I will leave this issue open.
I just checked the 10 relays with the lowest latency for me and none of them advertised nip50 support.
If you would like, You could check those relays compatibilities by using NIP-11 (or request with Accept header with application/nostr+json as value) to those relays,
And you should get the supported_nips containing nips that the relay could use:
{
"supported_nips": [
// ....
50,
// ....
]
}
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Probably implement NIP-50?
Simply adding
search
intofilters
object with search query:And then it return EVENTs that normal feed could parse easily
The text was updated successfully, but these errors were encountered: