yep,
I just wonder if it is really worth to have this special case.
why not have a NWC connection string in there (wouldn’t that also increase privacy actually?)
clients can easily validate the connection before adding it.
any current SDK would work and clients have NWC code anyway.
If something goes wrong and even one person loses their entire wallet by posting a real NWC string to their profile, saving a few lines of code will have been foolish. NWC strings themselves are already dangerous because they're a bearer token - everything should be using NWA anyway, and that wouldn't work for receiving zaps
I just don’t really see a difference that big actually.
it’s either way some lines of code somewhere that processes a nostr message.
but yea, people do crazy things… people loose sats by posting their seed phrases everywhere.
either way the nostr client could easily protect them.
It's a few lines at the wallet, or more lines in every nostr client
why more lines?
the wallet would implement a completely new way for the messages.
I'd rather open that PR myself than have anyone lose funds
which PR?
anyway let’s see if it happens.
still need to convince more wallets to implement NWC.
I think that I'm on to something with https://deposits.ynniv.com. If it works out, the next billion wallets will be NWC. So... I'm not worried about adoption
This is also why I'm interested in LNURL functionality natively available from NWC
