Anyone working on a fork of Amber or a new Android signer that doesn't invasively require a constant relay connection in the background? Or can this already be disabled? #asknostr

nostr:nevent1qvzqqqqqqypzqamkcvk5k8g730e2j6atadp6mxk7z4aaxc7cnwrlkclx79z4tzygqy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqyr8w50w7yt7465lt5nywz5l6svl94hjdfeneuhzc0783je8qpvs862ln448

Reply to this note

Please Login to reply.

Discussion

Amber does 2 things with relay connections:

1. It fetches your profile information so it can show your display name and profile picture to help you distinguish whick of your npubs you are selecting to sign for.

2. It sends and receives NIP-46 remote signing messages back and forth with clients you logged into using NIP-46. The background relay connections are required for this signing method.

If you don't use NIP-46 for logging into and signing requests for any clients, I'd imagine you can simply remove all of your active relays, but if you use NIP-46 remote signing, you will need to keep them connected so Amber will see when any new signimg requests come in.

nostr:nprofile1qqs827g8dkd07zjvlhh60csytujgd3l9mz7x807xk3fewge7rwlukxgpz9mhxue69uhkummnw3ezumrpdejz772u5wm is the one who would be able to confirm if there is a way to disable all relay connections in Amber, though.

You can also download the offline version

That's what I was looking for then 🙏