Oh, what is the error message? Maybe you can report it in github issue or tell #[5] personally. He will be happy if you help him report those bug/issue so satdress fork can be improved
Discussion
What are you using? Mine didn't crash in at least a week now and still running.
I think I was connecting to LNBits! 🐶🐾🫡
What version, what options? Did you enter a nostr pubkey?
Latest git pull from yesterday, yes pun key, yes nsec for NIP-57 notes! 🐶🐾🫡
Let me check now and give you a messages that I saw! 🐶🐾🫡
If you have get_nostr_profile on true, please set it to false, that needs some rework first. (It's only for getting nostr profile pictures to show in some ln wallets that support it). Other than that I'm running lnbits with nostr notifications pretty much stable here.
🐶🐾🫡
panic: interface conversion: interface {} is nil, not bool
goroutine 135 [running]:
main.WaitForInvoicePaid.func1()
/home/TMP/satdress/waitforinvoice.go:148 +0x1e0e
created by main.WaitForInvoicePaid
/home/TMP/satdress/waitforinvoice.go:23 +0xca
And I don’t think I set nostr profile to true, at least not explicitly! 🐶🐾🫡
Also, the zaps were DM notifications! That doesn’t sound right! 🐶🐾🫡
Yes that's how it works. I can't access your client.
My client? I mean NIP-57 was not working! Zaps weee not registering as the should have! 🐶🐾🫡
Yes but the notifications in the latest version, if enabled will send you Dms on nostr. You can chose if it sends every notification or only those with comments or those that are not zaps (or a combination of all)
Did you/ can you compile yourself?
I did compile myself from the latest git commit! 🐶🐾🫡
Thanks! I certainly will, just wanted to make sure that the errors were not on my side. Still need to debug a bit. Need to also try different connections! 🐶🐾🫡