How much demand is there for Kagi to index nostr content? #Search #AdFree #Privacy #SearchEngine #Kagi

Replies (31)

As an idealistic nostr developer, I'd like to see a relay-based solution, so that we get to keep using a single interface, run queries in parallel, and encourage competition and specialization.
It would be specially cool if you came up with your own way of displaying Nostr results in your search results since they don't have a webpage backing them and linking to one specific Nostr web client would be lame. was trying to be a sufficiently neutral solution for being linked to in traditional search results, but if you're going to support Nostr natively a native note view would be ideal.
i already appreciate that kagi returns far more relevant results for nostr related search queries eg. "nostr kinds". so nice! i welcome more nostr search capability 🙏
Probably not a lot initially because Nostr is stille quite small. But you serving results from nostr events may help grow adoption and that would drive demand for indexed content. Happy Kagi customer BTW and thrilled to see you on here
Yes, without linking to a specific client, with a neutral visualization like njump.me It would be cool if you also expose a relay with search capabilities (https://github.com/nostr-protocol/nips/blob/master/50.md). One more, maybe crazy idea: this search relay could also return generic web results* through notes generated and signed by Kagi, so users could search the web within their preferred Nostr client, share and comment results. Of course this would give Kagi a nice visibility. * Only when the filter set Kagi as author.
Bonus for your final crazy idea: eventually the Kagi web search results would function as a Nostr-based timestamped archive of search results across the web. You could view the history as "what links and page previews did 'search term X' return on 6 date in history". Even better (and crazier) of the pages themselves were converted to markdown and saved as events...
Kagi is increasingly open source: It's a gradual process but we're committed to it. With plans to open source Orion for example, we want to ensure the team has grown sufficiently to be able to maintain it in a productive and meaningful way (reliably manage pull requests, open issues, code reviews, etc.)