We can edit the NIP as time passes and new options are invented.

Should I change it on the NIP? And then the search_string is just a string, not an array.

Also I didn't get where you would put the options, like "option:no_spam". Maybe we should specify that the "key:value" syntax is reserved for options inside the search string, and relays could come up with new stuff later, like "not:keyword" to filter out posts containing these and so on (relays not supporting the "not" keyword should just ignore that, instead of returning notes containing the "not" word, for example).

For example, if I search for "cat" the relay may also want to send me a note containing the word "cats" and not only notes containing "cat".

You've already fetched that note if you're reading it!

But I see your point, could be a good idea, but sounds way too hacky.

I see a QR code now. What is in that?

Would be nice to have a QR code with my nprofile.

Go to any GitHub issue, drag your image to the textarea, it will give you a link, copy that and post on Nostr. Close the tab.

#[0] may I ask you what are the plans for nostr.band? It is not open-source, is it? Are you planning on making it a profitable business in the future?

Just stop expecting Nostr to be exactly like Twitter and you'll be fine.

Now I am reconsidering. I think it should be less specific. It should be something like: "you search, and whatever response the relay gives you, that's it, relays are free to use their own algorithms as they please". What do you think?

Maybe instead of "keywords" the attribute could be named "search_string".

Merged the NIP.

I don't know what is a "launch", but yes, the idea started in late 2021. You can look at the git history of the nostr repository.

What relay is that? The tagging didn't work.

I inspected the wrong note in the second screenshot, but the result is the same in the parent.

#[3]

Who is Will?

Gossip shows #[0]:

The tag at index 3 is #[0]:

But thinking better, the "content" of the event being replied to should probably be readable if you want to enable this. As it will end up showing in "social" clients.

So if you have other metadata for the pull-request event put it on tags, and make "content" be a readable thing.

I think yes.

You must click on each action and scroll to the bottom:

https://github.com/mikedilger/gossip/actions/runs/4020454756

See also #[2] and #[1].

I agree we need more ways for people to be informed about relays from others.

Although your client should always check whatever hints it has an keep track of in which relays each person is living.

I am happy when it is just a Shiba Inu.