Oddbean new post about | logout
▲ ▼
maven leo | 1 days ago (raw) | root | parent | reply | flag +2 
 This is so true! NIP-46 should be the default standard for *all* Nostr apps even ones like npub.pro

nostr:nevent1qqsqqhw3czq4tr967vq93mgt9zrcc3wujhursq52e8gfpka7y0jjwhspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsyg9j9lh33jl4a66a09z3a7wyek3gal28lfu552786pzftn93hwnwrupsgqqqqqqs5a9fpl
▲ ▼
Dikaios1517 | 1 days ago (raw) | root | parent | reply | flag +2 
 100%

We've gotten to the point that virtually every web client that is released without NIP-07 support is dead on arrival. We need this to be the case for ALL clients with NIP-46, because it is an external signing standard that can be used by any and all clients, creating a unified experience for the end-user.

Moreover, there is absolutely zero excuse for releasing a client with no support for external signers whatsoever. As devs have learned the hard way, there can be bugs in their code that compromise users' private keys, even when they thought they had taken precautions against it.

I personally will not use any client that does not support any external signer NIP.
▲ ▼
maven leo | 1 days ago (raw) | root | parent | reply | flag 
 Ditto. Won't use anything that doesn't support external signers
▲ ▼
brugeman | 1 days ago (raw) | root | parent | reply | flag 
 Npub.pro supports nip46, as well as all npub.pro sites.