Nostr Web Client

I'm using nsec.app too and it works fine. guess I need more data to fix your issue.

I'm on desktop now and I'm getting the same error. I tried login in using the remote signer nip05 flow on a tool I created (ngit) and I'm getting the same issue. nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5 is this an issue with Amber 3.1.8?

From my perspective the nip05 login not the normal remote signer login flow. Have you considered presenting a QR code, copying nostrconnect:// or nip55 nostr:npub18c556t7n8xa3df2q82rwxejfglw5przds7sqvefylzjh8tjne28qld0we7?

I suspect most Amber users don't have nip46 relays setup on the nip05. Defaulting to nsec.app relay feels centralising.

Reply to this note

Please Login to reply.

Discussion

greenart7c3 11mo ago

It's probably because it's always using the secret now and using nip 5 , clients doesn't know the secret it should use. You can try enabling listen for new connections in the settings.

nip05 login was deprecated in favor of the nostrconnect because of this. With nip05 login you don't have a secret, someone can spam you with login requests, you need a server and if you don't have your on domain you will need to trust the nip05 provider to use the relay you want.

The best example for a nostrconnect login for me it's nostrudel, it shows a qrcode and let you change the relay. This way the user is always in control and can use a local relay like citrine or a relay in his home computer

DanConwayDev 11mo ago

Yes, enabling that fixed it. Note: I read Enable as enabled at first. Maybe have a line through the icon or grey the text or something else visual to indicate it is off?