Mockup:

Hi. Please add a license to the project. Thanks!

It would be great if you could link to specific searches, like this:

• https://nos.today/?q=foo

I find myself in the situation where I want to link to certain generic thing on nostr, mostly search strings and/or hashtags.

Not sure what the prefix should be, here is how various search engines do it:

• https://www.google.com/search?q=foo
• https://duckduckgo.com/?q=foo
• https://nostrview.com/search?q=foo

URL param q as part of query string seems to be the default. Personally I would like something like nos.today/q/foo more (or even /s/foo), but that's probably just me.

User Story

As a nos.today search engine user who is collecting information, I would like a way to copy the noteID to clipboard, so that I can paste the noteID elsewhere & collect noteID of multiple events before I investigate each one in detail in my nostr client.

Acceptance Criteria

1. Nos.today has a copy noteID button adjacent to each note
2. If user taps/clicks on copy noteID button, noteID is transposed to memory/clipboard

User Story

As a nos.today search engine user who is collecting information, I would like a way to copy the npubs to clipboard, so that I can paste the npub elsewhere & collect npub of multiple users before I investigate each one in detail in my nostr client.

Acceptance Criteria

1. Nos.today has a copy npub button adjacent to each note
2. If user taps/clicks on copy npub button, npub is transposed to memory/clipboard

mockup
Clearly I am not a designer 😂

Hi, Would it be possible to have an API on nostr.today?

current UI

suggested UI

comments
If note contains a URL, URL should be clickable and lead to URL destination (not noteID)

Apparently these two relays also support NIP-50 search. It would be good to have them added to the default list of searchable relays.

There are concerns regarding HTML tag handling in the nos.today. While the security aspect appears to be satisfactory, there is a possibility of unintended behavior. This includes the risk of XSS attacks and the potential for unexpected outcomes when linking to external resources.

like this:

I entered https://nostr.build/av/nostr.build_7b67e3e6e8e7905a4a7781f0e89bf9a370c29c57ec84b342cf88798fe3a65fc6.mp4 in nos.today, and received noise as results.

I had to do "npm install linkifyjs --save" to make the build work. Please update the package.json. Thanks!