Search engine indexing (or the lack of it) also works against discoverability for users but also for nostr itself. Let's take X as an example. If I can't find a tweet but remember the author and some of the content of the tweet, odds are I'll find the tweet immediately through Google. For nostr this obviously doesn't apply and literally kills SEO and discoverability on a different level than just user discoverability.
How can we solve this? I don't know. Just throwing it out there.
I don’t have an android so I haven’t been able to try it out yet but kind of sounds like what nostr:npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy is working on? An all purpose Nostr browser ?! https://spring.site
A Nostr protocol browser is fantastic. I hope Spring gets more polished and we see more implementations of these in the future.
I don't think a nostr specific browser will solve content, user and nostr's discoverability through traditional crawlers and spiders. Then there is the matter of "duplicate" content which technically is everything on nostr since every client basically shows a duplicate of content received from relays. Nostr content is simply not being indexed by the engines.
Test it with searches like "The Grinder nostr" for example.
Thus content discovery is at this point almost non-existent for the average person searching the internet. Odds of them finding nostr outside of our circles are very low to non-existing at this time.
