I agree.
Oh, you have a client.
I have a hard time with these private messages. The server should be alive, I will check, but test first on https://payaddress.co to see if your setup works.
Thank you.
Yes, NIP-41 is not a panacea, but I think it can work fairly well if, for example, one creates their seed on one app, then just copy-pastes their first nsec key from that app and pastes in other apps, never inputs the seed anywhere.
I don't know what that is, I am a humble person.
Yes, the second option, I want Gossip to handle nostr: URLs when I click on them on the browser. I have no idea of how to implement that.
If you are talking about Drivechain this is not a fair statement. Drivechain is not about doing any of these things on Bitcoin.
I think it is unnecessary.
https://github.com/blakejakopovic/nostcat + https://git.jb55.com/nostril is also a good combination. Not good for kind-4 messages though.
Another cool possibility `nostr:nfilter1...` with an encoded Nostr filter. I am still thinking of a use case for it.
I think noscl doesn't have that capability. It needs more love.
Why are you trying to use noscl and not some other well-equipped client?
The :// part is actually useless and ugly. There are many other URL schemes that do not use it (and I think you can go without it for http too). We can just save the word by not typing 3 extra characters all the time.
Here's you NIP: https://github.com/nostr-protocol/nips/pull/186
I have a toy script that should run on every nostr: click, but regardless of that the browser will show a big prompt whenever I click on a link with a scheme it can't handle. That prompt is not showing on https://nostr.band.
I looked at the devtools and I saw it was an , but it didn't have an href, so I assumed you were doing something dynamic.
I think filtering on the relay side will still work better than on the client.
With that said, using reactions to signal stuff to to relays might be a good idea.
Good to know, but I am having trouble using it, I just get infinite loading screens. I'll try to reset all the locally stored data and try again.
It could work but I'm not very excited about this. I really hate these premade templates.