nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg where was that CLN + description hash (for lnurl etc.) discussion?

there is the same for LDK now again.

I feel like on that topic the spec and ln implementation are so far disconnection from actual usage.

to me this is throwing complexity at something and not solving the seemingly fundamental issue.

now suddenly there would be multiple ways on how calls are made and it adds implementation complexity at both ends.

which window.nostr implementation is not available very often?

can you show where?

nostr:npub14wxtsrj7g2jugh70pfkzjln43vgn4p7655pgky9j9w9d75u465pqvagcye where are the socks?

what does it solve? we put effort in to be available as early as browsers allow on load.

and this works:

https://gist.github.com/bumi/6bd2c76b8a83170e2471da50a79aec97

and this will bring UX problems like how to deal with prompts.

why should nostr clients check the description hash of the bolt11 in the zap?

What does this prevent/allow?

I am asking because we dropped the description hash in the lnurl.

And some ln implementations have issues with the description hash.

cc nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg

I use nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 with my new LDK based nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm wallet. thanks nostr:npub19hg5pj5qmd3teumh6ld7drfz49d65sw3n3d5jud8sgz27avkq5dqm7yv9p

programming money is just about to get to the next level.

yep, I was wondering if there are some libraries with some sugar around this.

yeah, you can still send and receive :D

but in the extension it shows you more transaction details, shows your the lightning address, your avatar, swaps had been there (currently not available sadly, though),...

Hey Golang people: is there a somewhat default library to do some in app pub/sub event based architecture (without some external queueing tool) pub/sub pattern? or do I just use the normal internal Go features?

thank youuu, and thanks for raising it!

that was very helpful.

is this on Android? - I am not sure if it works in the background. wondering what that notifications means there.

If you try to send from Alby maybe try to send it from a different device?

do you have the app open while receiving? (I am not sure, but it might need to be open)

I don't even know who all are involved!

but I love watching the live show in my player and streaming sats to mellow cassette right now.

yeah, what nostr:npub1a6c3jcdj23ptzcuflek8a04f4hc2cdkat95pd6n3r8jjrwyzrw0q43lfrr is pulling off here is huge! love it!

this should be fixed now. some users who did not refresh the login in the last days had this issue. The number was low that's why it slipped through the monitoring.

Can you confirm it works for you?

btw. you should also login with the Alby account - you will get some new features that are not available through the old lndhub setup.

was this resolved?

aad1b11c

thanks, can you help me debug this? and do it again? - maybe 2-3 more times today? this helps me to debug the requests.

let's inspect this. because that must be some error obviously.

can you try it again.

and btw. can I onboard you to your upcoming new product to test soon?