It offers adding new connections like this:
And then it uses specific relays. Standard is relay.nsec.app
Discussion
bizarre it would need to do this, I thought signing stayed on device? why does it need to go to the internet and back just to sign?
š¤·āāļø
nostr:nprofile1qqs827g8dkd07zjvlhh60csytujgd3l9mz7x807xk3fewge7rwlukxgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7auvdel nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0dv4ph5
Maybe just to provide another option for apps that expect this kind of signing?
Amber can do entirely local signing using NIP-55, but it also supports remote signing via NIP-46. It uses relays to transfer the unsigned data to Amber, then the data is signed locally and transferred back to the client via relays. The relays used can be selected by the user and can even use a local relay, such as Citrine.
That said, even using Amber for NIP-46 signing has been spotty for me. Not sure why. It is using a similar concept as Nostr Wallet Connect, which has always worked quite well, but remote signing often just fails for some reason.