Why is it that I am **constantly** searching “addrh2ksi61…” and “event1slapem8ai205…” and “npub1ka3008jdos…” in the search bar of basically any client and literally never get any results? 🤔

When something doesn’t “@“ properly or embed the way it should, all I see is the address/hash/pubkey/etc, but it seems like the basic search function on all the clients has no idea what to do with them, which seems really silly… is this just a coincidence that it’s not finding it for the same reason it’s not displaying it in the notes? Or does the search really not built to find identifiers for notes and users, just the names and text itself?

Reply to this note

Please Login to reply.

Discussion

Not sure what your relay set is but adding nostr.band in amethyst helps a lot. I think there are a very small set of relays that support search.

relay.nostr.band *

Haven't used this much so idk how well it works, but I bookmarked it sometime back because someone shared it & my search experiences have also been pretty bad

https://advancednostrsearch.vercel.app/

Have you tried primal?

I'm not sure it supports naddr yet but I think npub & note work (nevent also?) -- and due to catching most of the notes get displayed

primal.net and nostr.band have the best search I've found.

Grab the User’s npub, paste into nostr.band and add search words behind it.

Thank me later.

nostr.band is my go to resource for finding specific information on Nostr.

I run into this issue all the time too. especially when re-post notes (kind 6) don't have a relay hint. so I updated the search in noStrudel to handle nevent, npub, note, and nprofile

https://nostrudel.ninja/#/search

I think it's the way the protocol is designed.

I think most clients will eventually need to build & maintain a local database of users to overcome the issue. A table of npubs & meta data that have become significant to me is very useful.

Amethyst feels like it is starting to get better Inn this regard.