I don't trust the Alby extension. I am using it with my LNBITS node and it phones home a lot. Why does it have to go to getalby.com when I zap someone from my node? http://blossom.poster.place/c544a5a05ff25be8ca23694b1a41164aa02de5225075c91fede176ede38c979d.png
Red Flag for Privacy on Nostr. Blocking Alby at the network level (ADGuard Pihole) still lets you zap nostr:nevent1qvzqqqqqqypzqv78gsnl8v4h840r3ulxexguzg49t5syqu34daca5jdqugylk62qqyvhwumn8ghj7un9d3shjtnsdaehgetj9ecxcctrv5hsqgx0jg2qzywvum9jekltegvn9v88hcelhvsvxggq4jut7md5792rpyzvq3qk
What's the packet data? Does the zap fail if blocked ? 🤔
I am fairly certain you are routing your invoices along this path: Recipient-> Nostr relay-> getalby.com-> LNBits web server-> you LN node. I don't think LN bits can natively talk to a Nostr relay unless you paste that Gian LNURL into something like Amethyst. (most Nostr cloents have depricated LNURL for Lightning addresses). A lightning address needs a web server and a domain to host your invoice received data. if you don't trust any company you must host your own domain. Have some sort of web server on 24/7. use a program like Zaplocker to catch invoices and forward them to your Lightning node. and connect that to your LND instance. NWC and LND hub seem to be the most open and free software that does this but I understand the apprehension.
so many spelling errors ugh. your* LN node Giant* LNURL Nostr Clients*
You likely use the Alby fiat rates. Can you go to settings and disable fiat rates or use a different rate provider. In the rates we specifically use the Alby one to not make users request other sources without knowing it. and thanks for investigating this, this for sure is helpful for us to improve this and I am sure we can get better there. User privacy is very important to us, though we our main focus is at this point simplicity.
Does Alby Hub work on Fedora Linux