Mastodawn

@StevenB @ericpp
it actually is decoupled. you just would need to run a public LNURL server or HTTP API and such on your own. NWC makes it all easy to do or build on.
what do you miss?

Show thread

Steven Bell

Jun 5

@bumi @ericpp

You guys move so fast I have troubles keeping up with everything Hub can do.

Now my lnurl is steven@getalby.com, so to get an invoice I use the getalby.com server. I think I was also using the easier setup as demonstration on how easy it is to use Alby Hub, so I don't have the full block chain, I'm using the Alby hosted block chain. That also may be part of my issue.

Ideally, my lnurl could be steven@badass.com and the invoice request goes to `https://badass.com/lnurlp/steven/callback`

Show thread

bumi Jun 7

@StevenB @ericpp
you can do that.
everything like the block explorer is configurable.
and you can run some app for lnurl on your domain that connects with your hub through NWC.
(also podcast players could use NWC now directly.)

The NWC is huge. It's one of the reasons I've been pushing to move away from the node in the valueBlock and just using the lnaddress. You can still use keysend lnaddress with the .well-known/keysend route, but a lot of the nwc wallets don't support keysend yet, so the apps would start needing to support lnurlp as well. But the idea of bringing your wallet of choice into any app is so ideal.