Replying to Avatar fiatjaf

https://nostrum.pro and https://nostr.band are excellent search engines, but they really should add support for the nostr: link scheme instead of hardcoding web clients. The web client I use is not there, the desktop native client I use is not there and the Android client I use is not there either. The universal way forward is nostr:npub1... and nostr:nprofile1..., please!

Maybe a nostr:share?kind=1&content=Hello%20Nostr could work for universal sharing of templated or pre-filled event content/type. Not sure how most url handler registration works across apps/platforms/devices. Thoughts?

I think with more sharing functionality, it can really boost adoption.

Reply to this note

Please Login to reply.

Discussion

It could work but I'm not very excited about this. I really hate these premade templates.

I do to. I dislike having to select/copy/paste more - especially on phones. Tap share, then edit and send.

For news articles etc, ideally it’s just the title of the article and a url.

I would only consider this if client apps already offer ways for users to nicely build such filters in the UI. Once people can easily build, the need for sharing them will arise. Until then, i think it's overengineering.

Another cool possibility `nostr:nfilter1...` with an encoded Nostr filter. I am still thinking of a use case for it.

And another good example is users sharing client app mute/block filters. Kind of like ad block list for events. It likely needs a filter that supports content field regex tho.