Avatar
bumi
330fb1431ff9d8c250706bbcdc016d5495a3f744e047a408173e92ae7ee42dac
working on getalby.com - a browser extension with lightning and Nostr support

ah I see. but it stores it locally, doesn't it?

so why does it need to be signed?

Why is iris.to always asking me to sign a timestamp? what is it used for?

I mean like this:

await window.nostr.nip04.decrypt(...);

await window.nostr.nip04.decrypt(...);

this should work, doesn't it? but I guess you do this in a component that don't know of the other calls?

I am wondering what's the best practice here. because the user might be prompted.

hmm, do you have some code example? awaiting the promise does not work for you?

We are defensive there to prevent too many prompts for the user.

but I see that this can make it a bit harder for the developer.

If the user has an Alby lightning address and account then we give them also an onchain address that can be used to topup and we have a moonpay integration -> check your getalby.com dashboard (it currently can not be shown in the extension, yet)

Actually I found the issue and a fix will go out with the next release!

ah indeed Opera has some issue with Alby right now. We haven't officially release Alby for Opera. Opera seems to block Alby from closing the prompt. I'll add an issue and will debug this. thanks fore reporting!

Now any format is supported in Alby.

oh yeah! that's awesome! thanks for testing it and the help.

anything particular that you miss?

oh yes! you're just way ahead of time :)ย  you should update the issue now a year later .

he is on the XMPP and Fedi world. we should convince Kosmos to run a Nostr relay actually.