All these NIPs and still no catNIP 🤨
They’re two separate implementations of the same protocol (lightning).
It’s because M1s can run iOS apps, like Damus
#[0] thanks for making NWC available on Umbrel, super easy to install 🙌🏻
Damus donations setup via Nostr Wallet Connect ✅ ⭐️
Yesterday I finished reading https://www.goodreads.com/book/show/17333324-ancillary-justice I enjoy fiction about space-faring AI and this is an enjoyable one. One of those stories that’s heavy with obscure references that only become clear as you progress through the novel.
Added to my reading list!
#[3] LND_HOST should be of the form: https://xxx.onion:8080
Sounds like I need to update the documentation a bit more 😅
The latest docker image is: ghcr.io/hugomd/lnd-nostr-zapper:e8de5840
Accompanying documentation is available at: https://github.com/hugomd/lnd-nostr-zapper
The latest image is around ~30 MB, before it was somewhere in the range of ~800 MB! I was including all of the build tooling.. Oops!
I was posting a ‘developer update’, based on what I’ve worked on today.
The project is here: https://github.com/hugomd/lnd-nostr-zapper
The TL;DR; is: lnd-nostr-zapper is an application you can self-host to receive nostr zaps to your self-hosted Lightning Network Daemon (LND) node.
E.g. if you run an Umbrel node (https://umbrel.com), you could run this to receive zaps directly.
The latest docker image is: ghcr.io/hugomd/lnd-nostr-zapper:e8de5840
Accompanying documentation is available at: https://github.com/hugomd/lnd-nostr-zapper
I’ve spent some time today improving lnd-nostr-zapper:
- better documentation in the README
- reducing image size, using multi-stage docker builds
- starting tor within the application, instead of as a background process in alpine linux
- fixing certificate errors when using websockets over tor
I’ve been playing with WoS for sending test payments, but I’m definitely using lnd-nostr-zapper for receiving zaps ⚡️
Weekly reminder to please remain caffeinated ☕️
gn nostr 💤
Not at all, gn #[3] ! 🤙🏻