Add WebLN about stacker.news HOT 9 CLOSED

Let me know if you have questions. I am happy to help (you can also find me in the bitcoin design slack)

from stacker.news.

I was thinking of the most simple WebLN integration. (so without changing the concept that the user has an account and a balance).

we could simply check for webln on the QR topup page: https://github.com/stackernews/stacker.news/compare/master...bumi:webln?expand=1 (pseudo code - because I could not run it)

the idea is, that it checks of WebLN is available, if so it hands over to WebLN. if NOT it shows the current flow with the QR code

from stacker.news.

Thanks for this! This is roughly the level of change required to support WebLN? Much less work than I thought

from stacker.news.

Yeah, just call some JS instead of showing a QR code. + some error handling (and showing the QR code in the error case)

from stacker.news.

Right on, I'll reprioritize this. Might be able to cram it in today even.

from stacker.news.

Hey @bumi, deployed this. SN now supports both fund and withdrawals through WebLN. Tested it with Joule - seems to work well. Thanks for giving me the push!

Lmk if you have any gripes.

from stacker.news.

whoop whoop! you're fast. works great! 🎉
Though I would only show the QR code if WebLN is NOT available or the WebLN request fails. - I find doing both a bit confusing...

is there a reason why you do it like this? (In my code I tried to do that with the useWebln state.)

from stacker.news.

I don't disagree but a blank page is also confusing - in a different way. This is just version get.it.done. On my MacBook Air the popup from Joule covers most of the page, so it also didn't seem too confusing too. Up to changing it though if your experience differs significantly.

from stacker.news.

I'd show a loading spinner instead.

Our extension currently pretty quickly closes the popup after confirmation and it takes a second until the payment is done.
So I guess there the QR code is visible longer.
I also think the idea is that most should be handled in the website (e.g. also error handling) - so we do not wait but leave it up to the website.

from stacker.news.