Oddbean

I now only use #Amber as my event signer. On mobile, it manages access to my #nostr private key when on #Amethyst and on #0xchat. When on desktop, #NoStrudel calls Amber when it needs to sign something (with granular control for remembering an action if I so wish. If you're not using Amber, there's really nothing better right now.

That's right. I suppose given the login URL that Amber generates is your npub along with a Bunker nsec relay, it uses the two, so when noStrudel needs to sign something, it calls Amber on Android via the relay+npub, and Amber notifies you to allow/disallow as/when required.

No, there's no need. On Amber, click Add App. Give it a name, such as "noStrudel @ computer". It'll copy a link to your clipboard (essentially your npub @ relay). Input that link into noStrudel's Nostr "Connect/Bunker" sign-in option, under advanced. And you should get a notification on Amber to allow login. If the notification doesn't come through, go to Amber's settings and try direct connection. I have ntfy installed and working but Amber notifications aren't working through it for some reason, but direct connection works flawlessly.

Thanks, wow, It works with "direct connection" for me too. So basically the relay at nsec.app is just the medium to make Amber and the web client talk to each other, but then it's Amber that actually signs the events and sends them back to the web client, no private keys leave Amber right?

Precisely! Much better than giving an application an nsec or even using a browser extension. I hope all apps and websites incorporate it now that Amber's functionality has been formalized as NIP-46 for nostr.

Yeah, exactly. Btw, I also sent you a zap (manually this time, not through Amber or NWC this time, still need to figure that stuff out), but I was just wandering, do you see something in your balance? Because I can see sats are sent, but noStrudel is not showing me anything.

The 21sats? Yep, got it, thank you! I believe it may dependent on what relays are aware that the zap happened, I've had the same issue before. Unsure on the exact fix. Make sure you have a healthy number of relays, both big(for content discovery and indexing) and small (to help them grow), I've done the same and have seen a drastic improvement in zap/reaction awareness and content regardless of which client I use at any given time.

I don't think it is because of the relay choice, I think the problem here is in the "private" nature of the payment, maybe the wallet used and therefore the corresponding LN payment needs to be done in a way that is recorded as coming from the right nostr profile, so that the event can be associated with it and then be displayed/retrieved. Otherwise it is considered a "rogue" payment, but this is just my two cents.

Hum.. Accodiing to NIP-57 (the implementation of zaps), notes/events include payment related tags, of which include the amount, lnurl and also relays. My understanding is if a payment is received on that address (unique to the post), it is known by the relays included. I can't see any zaps on these posts from you, but I did receive it - Did you zap a specific post or my profile? If it was a post, can you link it?

It was this post: nevent1qvzqqqqqqypzpte8562wrm20dljp9yqnnfypnvvzmsumalvas40hrq5923km5ly0qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmwdaehgu3wdau8gu3wv3jhvtcqypuyg9wz485xtsxc9fw88zpmtl9cg4gnrn7allryac7whpn4vft8sjkvgwr

I did some troubleshooting yesterday on an issue that may have been related, essentially some inconsistency with how my LN address worked. It may have had an effect on this particular issue, so if that's the case, shouldn't happen anymore. Otherwise, really don't know.. 🤔