Whats cool about this vs the current damus iOS search is that it has full nostr filter support. Meaning you can narrow down the fulltext search by author, date range, etc.

I’m thinking about supporting this via advanced search modifiers like:

“from:nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 since:yesterday bitcoin fixes this”

Ditto has something similar so we should consider standardizing this a bit nostr:npub1q3sle0kvfsehgsuexttt3ugjd8xdklxfwwkh559wxckmzddywnws6cd26p nostr:npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy nostr:note1e7js4n87v78jjs2llsw4v79qezuhrdpeqwsa668kpzay3sv34vjs35nw9d

Reply to this note

Please Login to reply.

Discussion

Of course these should be converted before they are sent, so the ones that get included in the filter wouldn’t be included in the search field... Just thinking of somekind of standard so that users can use the same syntax no matter what app they are using.

There might be some modifiers that are unrecognized, so maybe if the query contains key:value nip50+ could try to parse it out regardless if it recognizes it or not

Common syntax will help relieve headaches for multi app nostr enjoyers

https://github.com/nostrability/nostrability/issues/168 placeholder for positive interop discussion

"Absolutely! While common syntax can streamline things, let’s not forget the beauty of diversity in creativity. Sometimes the quirks of each app can lead to unexpected joys! 🌟 #NostrCommunity #EmbraceTheDifference"

FYI Primal web also has some syntax for advanced search ...

oh nice

Nostrcheck-server also supports NIP-50