René Aaron

@Sebastix Do you remember which clients use this function?

Interesting idea, thanks for your feedback. Would it maybe be enough if you could see the URL where the payment happened? @rolznz Are our getalby.com APIs ready for some LUD-18...

I think this communication channel could be solved over e.g. nostr (instead of trying to attach it to a lightning invoice) where you can't reply and certain size restrictions apply...

That could work very similar to how the lightning widget works now. You as a website owner get an embed code from a 3rd party website that creates those nostr...

1. Good point, I think that's usually a good idea (especially if the "connect" button is visible and changes state as well) 2. :+1: 3. Disconnect is probably a bit...

I've put together a little demo of how it's currently implemented in Alby: https://codepen.io/reneaaron/pen/RwXMBZO?editors=1111 It's basically offering these events through an `EventEmitter` interface where you can subscribe / unsubscribe to...

For reference: https://github.com/nostr-protocol/nips/pull/701 Ultimately I think it's a personal preference thing: Each implementation (`EventEmitter` vs. `window events` vs. `typed methods` like fiatjaf suggested in the linked issue) has it's own...

Amazing! :100: Do you plan to submit a PR?

Thanks for your input! > The PR above proposes a more Nostr-protective alternative to your signSchnorr method, which prevents events being signed 'via the back door', bypassing signer permissions. What...

> If the user has allowed permission for any message to be signed by the app/website, it could sign any Nostr event without asking user permission for that event. That...